Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12ae862606f77ee33dc9b59aca38993426a5c527a8abfe0531b32ea776e240c3

Tx prefix hash: beb8a3aaf017211b820b2c6777aeb603763fe18fc40d6168b5bdf1624ff7c6c1
Tx public key: a4d092901fbab8c9a3e1e29cc5ac5275f01a305970a024f0e7885c298913e227
Timestamp: 1750112523 Timestamp [UCT]: 2025-06-16 22:22:03 Age [y:d:h:m:s]: 00:157:09:22:15
Block: 1306532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110267 RingCT/type: yes/0
Extra: 01a4d092901fbab8c9a3e1e29cc5ac5275f01a305970a024f0e7885c298913e227021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 462c67395814a4d03afec4812c3cdfa9ca5cc5c0fe41cf47cc4e02c683aa37bc 0.600000000000 1794139 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": 1306542, "vin": [ { "gen": { "height": 1306532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "462c67395814a4d03afec4812c3cdfa9ca5cc5c0fe41cf47cc4e02c683aa37bc" } } ], "extra": [ 1, 164, 208, 146, 144, 31, 186, 184, 201, 163, 225, 226, 156, 197, 172, 82, 117, 240, 26, 48, 89, 112, 160, 36, 240, 231, 136, 92, 41, 137, 19, 226, 39, 2, 17, 0, 0, 0, 2, 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