Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e215110165a352a703099e1c6f65026e808c25c47bcb993605e9b0c70066f759

Tx prefix hash: 4da014998b0bacdabb1c06098cc1fa7d9821f07d52a4e54f6c42ce9f26092905
Tx public key: 4ac0703e8be4edb7ba34aef62471367c5a7f2ff52df9a803e151b02e2905c4c1
Timestamp: 1703403696 Timestamp [UCT]: 2023-12-24 07:41:36 Age [y:d:h:m:s]: 01:114:04:07:47
Block: 919964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342725 RingCT/type: yes/0
Extra: 014ac0703e8be4edb7ba34aef62471367c5a7f2ff52df9a803e151b02e2905c4c10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5efd2dced155bed6591f8e0676900d8c74e59e749b9887950624c7777ab4cbeb 0.600000000000 1377642 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": 919974, "vin": [ { "gen": { "height": 919964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5efd2dced155bed6591f8e0676900d8c74e59e749b9887950624c7777ab4cbeb" } } ], "extra": [ 1, 74, 192, 112, 62, 139, 228, 237, 183, 186, 52, 174, 246, 36, 113, 54, 124, 90, 127, 47, 245, 45, 249, 168, 3, 225, 81, 176, 46, 41, 5, 196, 193, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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