Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd8cbe49c9b9060b4d5a8c36be89b7b3ccc8045c7cbc01b2de0deb2ef58b798

Tx prefix hash: 0e53c4b1dffc3c15d1a657152dc891768a2ba229ffc21dbdb92a24ca4e64f943
Tx public key: 1e24bdb8db1603516d89c83416344f827d8d29dfddafed7c06dc0ca1587fc630
Timestamp: 1711737316 Timestamp [UCT]: 2024-03-29 18:35:16 Age [y:d:h:m:s]: 00:286:19:06:07
Block: 989072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205273 RingCT/type: yes/0
Extra: 011e24bdb8db1603516d89c83416344f827d8d29dfddafed7c06dc0ca1587fc6300211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cd5812b6387a16c6c057024393b434226c8bed8cfa5e7fedbe3c0fd51c357f6 0.600000000000 1449367 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": 989082, "vin": [ { "gen": { "height": 989072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cd5812b6387a16c6c057024393b434226c8bed8cfa5e7fedbe3c0fd51c357f6" } } ], "extra": [ 1, 30, 36, 189, 184, 219, 22, 3, 81, 109, 137, 200, 52, 22, 52, 79, 130, 125, 141, 41, 223, 221, 175, 237, 124, 6, 220, 12, 161, 88, 127, 198, 48, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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