Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e963defae8823bedd5194a4c7211ad22201b62cb5ab0aa19045171eea15ea137

Tx prefix hash: bc309f59ff99a59941b290e2c0c940a8d86f85709f2c940094f0ae595efe26b7
Tx public key: 7c6498eb7df9c60a4f3710dae90450a1ec0d543262bda125c4773504c4184ed4
Timestamp: 1722307893 Timestamp [UCT]: 2024-07-30 02:51:33 Age [y:d:h:m:s]: 00:246:04:02:02
Block: 1076687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175827 RingCT/type: yes/0
Extra: 017c6498eb7df9c60a4f3710dae90450a1ec0d543262bda125c4773504c4184ed402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ec27008cdb59a671493d1df1eb84897c027a84e3f0bc5b2a362bc99ffe67078 0.600000000000 1549228 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": 1076697, "vin": [ { "gen": { "height": 1076687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ec27008cdb59a671493d1df1eb84897c027a84e3f0bc5b2a362bc99ffe67078" } } ], "extra": [ 1, 124, 100, 152, 235, 125, 249, 198, 10, 79, 55, 16, 218, 233, 4, 80, 161, 236, 13, 84, 50, 98, 189, 161, 37, 196, 119, 53, 4, 196, 24, 78, 212, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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