Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baea4a69970b8944518ae90f8d3bf31795cf0de29e6fbcf65fbc9fcedb30f2bf

Tx prefix hash: bcbd226603090139c4574936b938d0df1fe5d8087f62b20826441cc6226360c9
Tx public key: d7ef47d95cb54027f230d09b3c9af3d9d22685d00e22899e9c0923f94054f95a
Timestamp: 1734686502 Timestamp [UCT]: 2024-12-20 09:21:42 Age [y:d:h:m:s]: 00:172:20:05:11
Block: 1179221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123322 RingCT/type: yes/0
Extra: 01d7ef47d95cb54027f230d09b3c9af3d9d22685d00e22899e9c0923f94054f95a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 882800a4ab4520ae92ee44cbf1148a465226cf23c928d840e8e1534506039d04 0.600000000000 1665612 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": 1179231, "vin": [ { "gen": { "height": 1179221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "882800a4ab4520ae92ee44cbf1148a465226cf23c928d840e8e1534506039d04" } } ], "extra": [ 1, 215, 239, 71, 217, 92, 181, 64, 39, 242, 48, 208, 155, 60, 154, 243, 217, 210, 38, 133, 208, 14, 34, 137, 158, 156, 9, 35, 249, 64, 84, 249, 90, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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