Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3edf213359a87c82e3e4087b39b177e6754f49a8b1ca2708d3ebe24448bbaa

Tx prefix hash: 4e2804840d23e543f694441577927d0968e34c19102005ddcd8170a69247c5f6
Tx public key: d3d8166cc00429d6f0ced3b2fe178e23d4a14c0ec3cf5893f1f4115a3e8ae3a3
Timestamp: 1762693667 Timestamp [UCT]: 2025-11-09 13:07:47 Age [y:d:h:m:s]: 00:058:22:42:34
Block: 1408380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42211 RingCT/type: yes/0
Extra: 01d3d8166cc00429d6f0ced3b2fe178e23d4a14c0ec3cf5893f1f4115a3e8ae3a30211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a9d12f5e389465a4ff2cec357bdf5fa5d2036029e7ebf739f9328ba12c9c3e 0.600000000000 1896809 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": 1408390, "vin": [ { "gen": { "height": 1408380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a9d12f5e389465a4ff2cec357bdf5fa5d2036029e7ebf739f9328ba12c9c3e" } } ], "extra": [ 1, 211, 216, 22, 108, 192, 4, 41, 214, 240, 206, 211, 178, 254, 23, 142, 35, 212, 161, 76, 14, 195, 207, 88, 147, 241, 244, 17, 90, 62, 138, 227, 163, 2, 17, 0, 0, 0, 3, 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