Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c781e73cf45936e514a4192891cd6e03c95f6c186cd9d4a5a3045071174a1be5

Tx prefix hash: 7311e6fc7089136cd76d8a16cfbd3f504f2b72c282f16fc9245bb0e2c94c6691
Tx public key: 27a5016bab1809c4ffd3de43ae8a89e8b9105e5bb8533f00cd38a8714848e35e
Timestamp: 1702942008 Timestamp [UCT]: 2023-12-18 23:26:48 Age [y:d:h:m:s]: 01:148:01:54:55
Block: 916138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366983 RingCT/type: yes/0
Extra: 0127a5016bab1809c4ffd3de43ae8a89e8b9105e5bb8533f00cd38a8714848e35e021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f940ab47ae0de7042f9b8759ffa7f4bb7a40ad18548323e01c8430f97347d08d 0.600000000000 1373616 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 916148, "vin": [ { "gen": { "height": 916138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f940ab47ae0de7042f9b8759ffa7f4bb7a40ad18548323e01c8430f97347d08d" } } ], "extra": [ 1, 39, 165, 1, 107, 171, 24, 9, 196, 255, 211, 222, 67, 174, 138, 137, 232, 185, 16, 94, 91, 184, 83, 63, 0, 205, 56, 168, 113, 72, 72, 227, 94, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8