Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57cb9805daccdbef02b01a4eb14c194be8e4d9662458a107c50b0b108be1fd93

Tx prefix hash: 8ab795effc21e7bb91c7cfe2f1279836906cd4ee213622e8b58bf82123bfe63a
Tx public key: dbb38496c28a79bc9abf73d332e3e0bb124767510e67d1dcc64cfc0e19a03c39
Timestamp: 1760954731 Timestamp [UCT]: 2025-10-20 10:05:31 Age [y:d:h:m:s]: 00:038:20:28:06
Block: 1393985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27806 RingCT/type: yes/0
Extra: 01dbb38496c28a79bc9abf73d332e3e0bb124767510e67d1dcc64cfc0e19a03c39021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ed1bd92def4f7be55dd1f1bfbd3c0b2d9f8916ba6f2c6a0b9e6df2640404603 0.600000000000 1882252 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": 1393995, "vin": [ { "gen": { "height": 1393985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ed1bd92def4f7be55dd1f1bfbd3c0b2d9f8916ba6f2c6a0b9e6df2640404603" } } ], "extra": [ 1, 219, 179, 132, 150, 194, 138, 121, 188, 154, 191, 115, 211, 50, 227, 224, 187, 18, 71, 103, 81, 14, 103, 209, 220, 198, 76, 252, 14, 25, 160, 60, 57, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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