Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 953e9a6c16d0ed8ab4d9e99b8e161a0b5166b2cdfea05db89f8efa9f3d3d40c9

Tx prefix hash: 496f5d777871ec014d6a90a388e26c6fe2076517daaf08f83b32e976fbe29157
Tx public key: ba9ae635c14737520f1601abc9e6da09300a6a87bcff70f744ddabb2c469012c
Timestamp: 1742019099 Timestamp [UCT]: 2025-03-15 06:11:39 Age [y:d:h:m:s]: 00:292:13:00:06
Block: 1239648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206863 RingCT/type: yes/0
Extra: 01ba9ae635c14737520f1601abc9e6da09300a6a87bcff70f744ddabb2c469012c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aa7bf87c46edeb4e18e11107a9a8ee9a0233636a323aaaf700713d1f2e60331 0.600000000000 1726613 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": 1239658, "vin": [ { "gen": { "height": 1239648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa7bf87c46edeb4e18e11107a9a8ee9a0233636a323aaaf700713d1f2e60331" } } ], "extra": [ 1, 186, 154, 230, 53, 193, 71, 55, 82, 15, 22, 1, 171, 201, 230, 218, 9, 48, 10, 106, 135, 188, 255, 112, 247, 68, 221, 171, 178, 196, 105, 1, 44, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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