Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d9ab2520ee670f61aa5e0e812b32f0ff9116b778da457c8c962a6254087239d

Tx prefix hash: 44baf0e9c3fffd908c330448f581959d566f5a140196a15589dabbd7bb8e6f16
Tx public key: dc111200db3565ae6063c83d519beed24c8bf31f41bd69fcc9983cd2a00c98c9
Timestamp: 1738164087 Timestamp [UCT]: 2025-01-29 15:21:27 Age [y:d:h:m:s]: 00:296:09:00:33
Block: 1207731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209576 RingCT/type: yes/0
Extra: 01dc111200db3565ae6063c83d519beed24c8bf31f41bd69fcc9983cd2a00c98c90211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df4f3dd38f0be9a8fb325d258d9337eb260d9e7a8ab895871aa847df2bd9cf9 0.600000000000 1694456 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": 1207741, "vin": [ { "gen": { "height": 1207731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df4f3dd38f0be9a8fb325d258d9337eb260d9e7a8ab895871aa847df2bd9cf9" } } ], "extra": [ 1, 220, 17, 18, 0, 219, 53, 101, 174, 96, 99, 200, 61, 81, 155, 238, 210, 76, 139, 243, 31, 65, 189, 105, 252, 201, 152, 60, 210, 160, 12, 152, 201, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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