Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6277d5810ea83dbe10722f13d336c0ef4ba559585c7f0f3ca3a7425ca3b657aa

Tx prefix hash: db8dcd17e542a8b9f178f100fa09bfa77b1bbd99e9d01286b3979e9cf59871a7
Tx public key: b5c6835a0c7dbd8f48672ab192853d8b986f6aeaf1c67edebba8aa17ec92cf33
Timestamp: 1749384832 Timestamp [UCT]: 2025-06-08 12:13:52 Age [y:d:h:m:s]: 00:158:19:25:51
Block: 1300624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111185 RingCT/type: yes/0
Extra: 01b5c6835a0c7dbd8f48672ab192853d8b986f6aeaf1c67edebba8aa17ec92cf33021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69878d659ef986e8b30905ba7c716484c8d09d92e387a140c154b91b0ddd8bae 0.600000000000 1788173 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": 1300634, "vin": [ { "gen": { "height": 1300624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69878d659ef986e8b30905ba7c716484c8d09d92e387a140c154b91b0ddd8bae" } } ], "extra": [ 1, 181, 198, 131, 90, 12, 125, 189, 143, 72, 103, 42, 177, 146, 133, 61, 139, 152, 111, 106, 234, 241, 198, 126, 222, 187, 168, 170, 23, 236, 146, 207, 51, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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