Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fffc4f66ca44e9f11e95e4d5ae26465a5c6cb126436f95ad581ae0bc1d77a22

Tx prefix hash: a320c05cbe684840864d80fd3edd86c6080960ee694ae0d7bcc64ea1c345497a
Tx public key: b11b1a5d26499fd9da8267dc03a1ce5eb068735c43ac910e989dba15d597c737
Timestamp: 1728574962 Timestamp [UCT]: 2024-10-10 15:42:42 Age [y:d:h:m:s]: 01:028:11:22:20
Block: 1128646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278723 RingCT/type: yes/0
Extra: 01b11b1a5d26499fd9da8267dc03a1ce5eb068735c43ac910e989dba15d597c73702110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7103dac5bbbf9c8b8e7646b8d9e9ac9b59077cd8e57d53ff2f8d6842efeb6736 0.600000000000 1611465 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": 1128656, "vin": [ { "gen": { "height": 1128646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7103dac5bbbf9c8b8e7646b8d9e9ac9b59077cd8e57d53ff2f8d6842efeb6736" } } ], "extra": [ 1, 177, 27, 26, 93, 38, 73, 159, 217, 218, 130, 103, 220, 3, 161, 206, 94, 176, 104, 115, 92, 67, 172, 145, 14, 152, 157, 186, 21, 213, 151, 199, 55, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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