Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e9b90deb1b365a1c2e54c2e7c78aa91caa602936c21299b40903acafe3c12dd

Tx prefix hash: 0e07a730905ce31f8314bba0b9da37910f4a9a8351f6cf53f73e82b4470c3481
Tx public key: dd7cc3a9fb7e5f13b8bc0f7a4af9e99de3951cd1a041e60bb7d0e0e8e93aad75
Timestamp: 1710815192 Timestamp [UCT]: 2024-03-19 02:26:32 Age [y:d:h:m:s]: 00:239:08:47:16
Block: 981426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171351 RingCT/type: yes/0
Extra: 01dd7cc3a9fb7e5f13b8bc0f7a4af9e99de3951cd1a041e60bb7d0e0e8e93aad7502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ed232596d52e919ab6edd156779cc533b93b41ca4c40be5549d21be00a05d75 0.600000000000 1441521 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": 981436, "vin": [ { "gen": { "height": 981426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ed232596d52e919ab6edd156779cc533b93b41ca4c40be5549d21be00a05d75" } } ], "extra": [ 1, 221, 124, 195, 169, 251, 126, 95, 19, 184, 188, 15, 122, 74, 249, 233, 157, 227, 149, 28, 209, 160, 65, 230, 11, 183, 208, 224, 232, 233, 58, 173, 117, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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