Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a364e591e4745a006cd8c0ecd1208a36df19d0d5c78c01cd361292690e37bb3a

Tx prefix hash: 0441756e72d85827b4bc85e3c1a3db237c6e38c7a9900572957e7888bb3a266d
Tx public key: 67040c6488a36798ff83336beb27552cdec274cb11b7686daf17a3b9b28ff53f
Timestamp: 1758942858 Timestamp [UCT]: 2025-09-27 03:14:18 Age [y:d:h:m:s]: 00:010:20:16:48
Block: 1377295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7759 RingCT/type: yes/0
Extra: 0167040c6488a36798ff83336beb27552cdec274cb11b7686daf17a3b9b28ff53f021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52fe997862ddc4d039de9a96db1f7f9bae5a8f8943c0a13f1e6f4e0cf222226e 0.600000000000 1865386 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": 1377305, "vin": [ { "gen": { "height": 1377295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52fe997862ddc4d039de9a96db1f7f9bae5a8f8943c0a13f1e6f4e0cf222226e" } } ], "extra": [ 1, 103, 4, 12, 100, 136, 163, 103, 152, 255, 131, 51, 107, 235, 39, 85, 44, 222, 194, 116, 203, 17, 183, 104, 109, 175, 23, 163, 185, 178, 143, 245, 63, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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