Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5099780d7588c767347e9c02adf3c59bd5dd9e241edfe4bf5d9cdb100531a2f6

Tx prefix hash: 62ddb648314a38fbf11d155e9cf81f45118db9e6b0f63271bf776f3730c509d9
Tx public key: fdf179657a4ba053c4fd6607d69bc216b371a04ac7bf420cb7a1cab69de1633b
Timestamp: 1732554431 Timestamp [UCT]: 2024-11-25 17:07:11 Age [y:d:h:m:s]: 00:137:09:40:10
Block: 1161533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98027 RingCT/type: yes/0
Extra: 01fdf179657a4ba053c4fd6607d69bc216b371a04ac7bf420cb7a1cab69de1633b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26c15d5f863eaffced65d17af191a1c8541fdc309afcb686505a79b242bf0768 0.600000000000 1647188 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": 1161543, "vin": [ { "gen": { "height": 1161533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26c15d5f863eaffced65d17af191a1c8541fdc309afcb686505a79b242bf0768" } } ], "extra": [ 1, 253, 241, 121, 101, 122, 75, 160, 83, 196, 253, 102, 7, 214, 155, 194, 22, 179, 113, 160, 74, 199, 191, 66, 12, 183, 161, 202, 182, 157, 225, 99, 59, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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