Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69bf66b3d320071d40bbd357f82d6c4d9e23284f2cb48e47de992f2608f4ab82

Tx prefix hash: 57491316c5a25ba3a063323f9b6a90ea38c4e883a6559946abe77de2f0eedaec
Tx public key: 69e2c58abb12054642918c445ab9dc5e511482401fdc3a905e7ead191fdcc0cf
Timestamp: 1717070671 Timestamp [UCT]: 2024-05-30 12:04:31 Age [y:d:h:m:s]: 00:153:15:24:19
Block: 1033275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109960 RingCT/type: yes/0
Extra: 0169e2c58abb12054642918c445ab9dc5e511482401fdc3a905e7ead191fdcc0cf02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8994a882b49f7335042b5707260a977beaa5c35670f75fdbcbdb66d46752f305 0.600000000000 1501738 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": 1033285, "vin": [ { "gen": { "height": 1033275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8994a882b49f7335042b5707260a977beaa5c35670f75fdbcbdb66d46752f305" } } ], "extra": [ 1, 105, 226, 197, 138, 187, 18, 5, 70, 66, 145, 140, 68, 90, 185, 220, 94, 81, 20, 130, 64, 31, 220, 58, 144, 94, 126, 173, 25, 31, 220, 192, 207, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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