Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25ec4bf4479e0f57fe3cecda91f6597bb764275c6911e9108ac6bf4a8e2c9020

Tx prefix hash: b9f3532895deb1a87b5ed1ce0339374c2e92ec99615554c7a95123b7b21edc23
Tx public key: 76902cc820827b2a6d9bb10a2eb813e5d113aba1d9abd11a9be9ec83c54626ff
Timestamp: 1741246186 Timestamp [UCT]: 2025-03-06 07:29:46 Age [y:d:h:m:s]: 00:259:14:30:31
Block: 1233237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183281 RingCT/type: yes/0
Extra: 0176902cc820827b2a6d9bb10a2eb813e5d113aba1d9abd11a9be9ec83c54626ff021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22ebc893ab0acf7bf9ac98ba7ee27631af6c68ecdaf26e1144fb6369c04df5c7 0.600000000000 1720156 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": 1233247, "vin": [ { "gen": { "height": 1233237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22ebc893ab0acf7bf9ac98ba7ee27631af6c68ecdaf26e1144fb6369c04df5c7" } } ], "extra": [ 1, 118, 144, 44, 200, 32, 130, 123, 42, 109, 155, 177, 10, 46, 184, 19, 229, 209, 19, 171, 161, 217, 171, 209, 26, 155, 233, 236, 131, 197, 70, 38, 255, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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