Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbfa307ee4d7677f2d9d3895ff0917c64a8055cdff17c07d6b8f0c04bffe21e8

Tx prefix hash: e7c7dc68ce263aff78d49dab8aa081aa35b09c61c9d400bcf966c11dda9b0d76
Tx public key: a2d7867e0dda79bd22554f3bf270707dfff70af2a55f3dbb0467a1a3cc1bf815
Timestamp: 1710256844 Timestamp [UCT]: 2024-03-12 15:20:44 Age [y:d:h:m:s]: 01:240:11:50:17
Block: 976786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430587 RingCT/type: yes/0
Extra: 01a2d7867e0dda79bd22554f3bf270707dfff70af2a55f3dbb0467a1a3cc1bf81502110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54d7347cb6d44bce993c92ee36ee54ec39b45ad0e99afa6f163c6d1cff24aee6 0.600000000000 1436783 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": 976796, "vin": [ { "gen": { "height": 976786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54d7347cb6d44bce993c92ee36ee54ec39b45ad0e99afa6f163c6d1cff24aee6" } } ], "extra": [ 1, 162, 215, 134, 126, 13, 218, 121, 189, 34, 85, 79, 59, 242, 112, 112, 125, 255, 247, 10, 242, 165, 95, 61, 187, 4, 103, 161, 163, 204, 27, 248, 21, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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