Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d25789faf562ee3973508a57f45a853edb7ede3ed60fbe847682a2693164b4ab

Tx prefix hash: 37e339e9cfc8ca0d7cee083313c3e70f8d6c6f23ff9aaa3c07cb039e5c7f9c00
Tx public key: 73b8f3130244c0327f03ab493ec7f17b5ce8bc1d64ba5a84216c34e818f3d4aa
Timestamp: 1648426626 Timestamp [UCT]: 2022-03-28 00:17:06 Age [y:d:h:m:s]: 02:237:07:13:54
Block: 467848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689116 RingCT/type: yes/0
Extra: 0173b8f3130244c0327f03ab493ec7f17b5ce8bc1d64ba5a84216c34e818f3d4aa02110000000ca272b9cb000000000000000000

1 output(s) for total of 17.291219173000 dcy

stealth address amount amount idx
00: a062946aa88b26989e9182f078b7ca6fb85c17e28ea7165450be84c5f2b071de 17.291219173000 886433 of 0

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": 467858, "vin": [ { "gen": { "height": 467848 } } ], "vout": [ { "amount": 17291219173, "target": { "key": "a062946aa88b26989e9182f078b7ca6fb85c17e28ea7165450be84c5f2b071de" } } ], "extra": [ 1, 115, 184, 243, 19, 2, 68, 192, 50, 127, 3, 171, 73, 62, 199, 241, 123, 92, 232, 188, 29, 100, 186, 90, 132, 33, 108, 52, 232, 24, 243, 212, 170, 2, 17, 0, 0, 0, 12, 162, 114, 185, 203, 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