Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb40995dd3a5cc50399435eb57e881bb4984e3d1bc5dca5ed27ba07cf27d5364

Tx prefix hash: 83179cc1a4da381618dd9a3bf47fa0130f1b3aa8ad3a89213523cd7ca709fa4f
Tx public key: 2cb9c3198f4ddc359be9e36f171a156c582bdabe31257bedc139ecd1816ea71a
Timestamp: 1670269170 Timestamp [UCT]: 2022-12-05 19:39:30 Age [y:d:h:m:s]: 02:041:03:07:01
Block: 646160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551310 RingCT/type: yes/0
Extra: 012cb9c3198f4ddc359be9e36f171a156c582bdabe31257bedc139ecd1816ea71a02110000000283600029000000000000000000

1 output(s) for total of 4.436124012000 dcy

stealth address amount amount idx
00: b98acdfb2bfeb0bd4a00037fe9a8f5243d30900c26dc5d2bdf9202919bb56c2d 4.436124012000 1086371 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": 646170, "vin": [ { "gen": { "height": 646160 } } ], "vout": [ { "amount": 4436124012, "target": { "key": "b98acdfb2bfeb0bd4a00037fe9a8f5243d30900c26dc5d2bdf9202919bb56c2d" } } ], "extra": [ 1, 44, 185, 195, 25, 143, 77, 220, 53, 155, 233, 227, 111, 23, 26, 21, 108, 88, 43, 218, 190, 49, 37, 123, 237, 193, 57, 236, 209, 129, 110, 167, 26, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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