Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 537cc6fe43737e06b88ad31a524e270866e229e81f2f7bef96f7efec87c94982

Tx prefix hash: 340741e1a38b9d5c51d277ea6efbede0817407ee8d8377e94948853da1d216d6
Tx public key: 6d000216b65533c9d2bb26c72923d7e9420c54e00ebdae186dd6f7d458c361c0
Timestamp: 1705511702 Timestamp [UCT]: 2024-01-17 17:15:02 Age [y:d:h:m:s]: 01:074:06:10:20
Block: 937427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314156 RingCT/type: yes/0
Extra: 016d000216b65533c9d2bb26c72923d7e9420c54e00ebdae186dd6f7d458c361c002110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab8bca7842cc4acaac93cb744baeefa5eb515b910b65f3b651038bfb6cd09530 0.600000000000 1395481 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": 937437, "vin": [ { "gen": { "height": 937427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab8bca7842cc4acaac93cb744baeefa5eb515b910b65f3b651038bfb6cd09530" } } ], "extra": [ 1, 109, 0, 2, 22, 182, 85, 51, 201, 210, 187, 38, 199, 41, 35, 215, 233, 66, 12, 84, 224, 14, 189, 174, 24, 109, 214, 247, 212, 88, 195, 97, 192, 2, 17, 0, 0, 0, 11, 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