Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b5dc46786a8d67358590d4d2a18b03de48e17abf981c0afea0e5746fc9df24f

Tx prefix hash: a8a6b9aee53a105e7ff1bab21a7dfafa57e00aa5f09f6a88bf27d35011329c74
Tx public key: b68d4a4aed60674d349f222eaf586640ac7669960240fadce961cdb59e6561e4
Timestamp: 1703005933 Timestamp [UCT]: 2023-12-19 17:12:13 Age [y:d:h:m:s]: 02:021:02:30:53
Block: 916676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534874 RingCT/type: yes/0
Extra: 01b68d4a4aed60674d349f222eaf586640ac7669960240fadce961cdb59e6561e402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b59c6cc1a2f4c1be254c85991610b1168c4bbd935b38fa4c2d1dd5db370810c3 0.600000000000 1374236 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": 916686, "vin": [ { "gen": { "height": 916676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b59c6cc1a2f4c1be254c85991610b1168c4bbd935b38fa4c2d1dd5db370810c3" } } ], "extra": [ 1, 182, 141, 74, 74, 237, 96, 103, 77, 52, 159, 34, 46, 175, 88, 102, 64, 172, 118, 105, 150, 2, 64, 250, 220, 233, 97, 205, 181, 158, 101, 97, 228, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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