Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37d8d2cc234f2027c66359972ad3f6f0e1db6e6780f0cf40a6a59eb8ef90db23

Tx prefix hash: 6e4d42fdd2c084fdc7c266bc61828fe0c709bc9e74644c10e2b4bcc0eee17390
Tx public key: afcf7ddd33fbfadd2016e8e02e9b607fd922dd0b84c419077c9dfd9cdaa87988
Timestamp: 1710062917 Timestamp [UCT]: 2024-03-10 09:28:37 Age [y:d:h:m:s]: 01:059:07:57:37
Block: 975181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303399 RingCT/type: yes/0
Extra: 01afcf7ddd33fbfadd2016e8e02e9b607fd922dd0b84c419077c9dfd9cdaa879880211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 924f87500194f6e4a9aa497f8aa96d4604ea837f2c3847f6c4ab8539d0a6955e 0.600000000000 1435152 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": 975191, "vin": [ { "gen": { "height": 975181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "924f87500194f6e4a9aa497f8aa96d4604ea837f2c3847f6c4ab8539d0a6955e" } } ], "extra": [ 1, 175, 207, 125, 221, 51, 251, 250, 221, 32, 22, 232, 224, 46, 155, 96, 127, 217, 34, 221, 11, 132, 196, 25, 7, 124, 157, 253, 156, 218, 168, 121, 136, 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