Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b7a8e0d3fb46cc41878c41ff1b070d647cd43d2ee28ede94af9444bd0d9c84

Tx prefix hash: 80904359e06fd0276a6c26a6b244e815935c39b0c7101a833b53483bcc0c4995
Tx public key: d826cf2c60c1c16c4d1e3fd2df4438ffdfa1c30033ddf50070c3ad4c1bf869c8
Timestamp: 1578649603 Timestamp [UCT]: 2020-01-10 09:46:43 Age [y:d:h:m:s]: 04:325:12:55:45
Block: 42462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122108 RingCT/type: yes/0
Extra: 01d826cf2c60c1c16c4d1e3fd2df4438ffdfa1c30033ddf50070c3ad4c1bf869c80211000000094ac5aa02000000000000000000

1 output(s) for total of 443.921941507000 dcy

stealth address amount amount idx
00: 4ba91343302ef3cf75ddf2a2d8c2b72a9a01b74691b4c05361aad2042043a3f6 443.921941507000 76531 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": 42472, "vin": [ { "gen": { "height": 42462 } } ], "vout": [ { "amount": 443921941507, "target": { "key": "4ba91343302ef3cf75ddf2a2d8c2b72a9a01b74691b4c05361aad2042043a3f6" } } ], "extra": [ 1, 216, 38, 207, 44, 96, 193, 193, 108, 77, 30, 63, 210, 223, 68, 56, 255, 223, 161, 195, 0, 51, 221, 245, 0, 112, 195, 173, 76, 27, 248, 105, 200, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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