Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7094e970fbc40cd15d7a156d3fd99990051233e556f5d539c312363c93dfda0

Tx prefix hash: 7be79b369a808a9f81f4a6e7eda976a2f9299864ad3a805a9f945929e02dad68
Tx public key: a52074e41346c104a54cbde547a3e13c17afb26a7fdb9096c78d9f3f62b14f7f
Timestamp: 1762798939 Timestamp [UCT]: 2025-11-10 18:22:19 Age [y:d:h:m:s]: 00:082:02:04:46
Block: 1409255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58591 RingCT/type: yes/0
Extra: 01a52074e41346c104a54cbde547a3e13c17afb26a7fdb9096c78d9f3f62b14f7f021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e92b185127bfc84d4e4b0a21fcbb28125f6e5c63713f63446db2a80ea28e866 0.600000000000 1897696 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": 1409265, "vin": [ { "gen": { "height": 1409255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e92b185127bfc84d4e4b0a21fcbb28125f6e5c63713f63446db2a80ea28e866" } } ], "extra": [ 1, 165, 32, 116, 228, 19, 70, 193, 4, 165, 76, 189, 229, 71, 163, 225, 60, 23, 175, 178, 106, 127, 219, 144, 150, 199, 141, 159, 63, 98, 177, 79, 127, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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