Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac6848259c0e83cd084e4c9d8bd2e52f27a749ae481072a4cb44e94f4e1c40cd

Tx prefix hash: 07142697677e8033a6213516b1abb8f45495084edb075e76f865a12c32d4c515
Tx public key: 9d87a446fd874edf68be33f65f27ed2507d92ce058f8f0ee96dd9d944bb7e75c
Timestamp: 1763184737 Timestamp [UCT]: 2025-11-15 05:32:17 Age [y:d:h:m:s]: 00:038:16:49:54
Block: 1412453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27702 RingCT/type: yes/0
Extra: 019d87a446fd874edf68be33f65f27ed2507d92ce058f8f0ee96dd9d944bb7e75c021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dcc5012d6898b4df3060051a555fbb96071a57d1d450411571f9c73bc088cb4 0.600000000000 1900922 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": 1412463, "vin": [ { "gen": { "height": 1412453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dcc5012d6898b4df3060051a555fbb96071a57d1d450411571f9c73bc088cb4" } } ], "extra": [ 1, 157, 135, 164, 70, 253, 135, 78, 223, 104, 190, 51, 246, 95, 39, 237, 37, 7, 217, 44, 224, 88, 248, 240, 238, 150, 221, 157, 148, 75, 183, 231, 92, 2, 17, 0, 0, 0, 1, 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