Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bae31917e75381f0ad5f826baf3bf270fbfcf4f686327eca6df1bb3f274f7d8

Tx prefix hash: 44a70273ddbe3c988a9ee106910c6c7a85325a84e44dbdd740d56cd0d9c771b1
Tx public key: bb1efbfcb4b09917bb365afd433b8272410da0bb89eecb8f648252abca1e8bb3
Timestamp: 1704219681 Timestamp [UCT]: 2024-01-02 18:21:21 Age [y:d:h:m:s]: 01:090:21:00:08
Block: 926713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326068 RingCT/type: yes/0
Extra: 01bb1efbfcb4b09917bb365afd433b8272410da0bb89eecb8f648252abca1e8bb30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6552d5f44c52580aac49954f5e71e13542f43a742c0331167cd87353c4e19612 0.600000000000 1384509 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": 926723, "vin": [ { "gen": { "height": 926713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6552d5f44c52580aac49954f5e71e13542f43a742c0331167cd87353c4e19612" } } ], "extra": [ 1, 187, 30, 251, 252, 180, 176, 153, 23, 187, 54, 90, 253, 67, 59, 130, 114, 65, 13, 160, 187, 137, 238, 203, 143, 100, 130, 82, 171, 202, 30, 139, 179, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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