Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cfeb88355258954a55ace827cf12cbc4e060e26c84829c0c394eb519cd0020

Tx prefix hash: 4520a9a375a63ac30ecb4dc72d5baa8a2796ebc779c194b76e29b056ba925505
Tx public key: e2bd880537eecea2d17d09f8ce4fee3a10ff3e26b2f51c21582cd08e84cd6a5e
Timestamp: 1750784070 Timestamp [UCT]: 2025-06-24 16:54:30 Age [y:d:h:m:s]: 00:146:16:23:09
Block: 1311945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102769 RingCT/type: yes/0
Extra: 01e2bd880537eecea2d17d09f8ce4fee3a10ff3e26b2f51c21582cd08e84cd6a5e0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a9155d7d00bece8b28d958fbe46e6799240af628607a75f87e2f0e97924ee0c 0.600000000000 1799574 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": 1311955, "vin": [ { "gen": { "height": 1311945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a9155d7d00bece8b28d958fbe46e6799240af628607a75f87e2f0e97924ee0c" } } ], "extra": [ 1, 226, 189, 136, 5, 55, 238, 206, 162, 209, 125, 9, 248, 206, 79, 238, 58, 16, 255, 62, 38, 178, 245, 28, 33, 88, 44, 208, 142, 132, 205, 106, 94, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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