Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 774d03bfa5398398d944a568e262b47964796083fa4959c79419e99892b356b7

Tx prefix hash: d44eb7213956fd6ad8f32089a1a6772b302e76660174776651772f274a0b23b6
Tx public key: 80f339b3f8a07b9e4dbc952f8f7dec801bceb6ee6b79c5f5359e14dc0e05d042
Timestamp: 1582806390 Timestamp [UCT]: 2020-02-27 12:26:30 Age [y:d:h:m:s]: 04:313:14:38:47
Block: 73141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117321 RingCT/type: yes/0
Extra: 0180f339b3f8a07b9e4dbc952f8f7dec801bceb6ee6b79c5f5359e14dc0e05d042021100000011d81c26c0000000000000000000

1 output(s) for total of 351.286781554000 dcy

stealth address amount amount idx
00: 632e636b94b11e474ecb0df64772a824581ed116f7e7461741468889a3927921 351.286781554000 134835 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": 73151, "vin": [ { "gen": { "height": 73141 } } ], "vout": [ { "amount": 351286781554, "target": { "key": "632e636b94b11e474ecb0df64772a824581ed116f7e7461741468889a3927921" } } ], "extra": [ 1, 128, 243, 57, 179, 248, 160, 123, 158, 77, 188, 149, 47, 143, 125, 236, 128, 27, 206, 182, 238, 107, 121, 197, 245, 53, 158, 20, 220, 14, 5, 208, 66, 2, 17, 0, 0, 0, 17, 216, 28, 38, 192, 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