Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ee7038d66ec223cfab6b33816d239eb7737219df903dff42cb4c6773675a70d

Tx prefix hash: f4906c94852ed75dccab5e42c63f5992817b19052706a9259c21e045a76ef982
Tx public key: a573c4e09c0a8bd757ddc1c13bc09840fe5576a726cbc9a85dc0c5e78c10f69e
Timestamp: 1710040043 Timestamp [UCT]: 2024-03-10 03:07:23 Age [y:d:h:m:s]: 00:350:14:04:12
Block: 974993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250645 RingCT/type: yes/0
Extra: 01a573c4e09c0a8bd757ddc1c13bc09840fe5576a726cbc9a85dc0c5e78c10f69e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8988b741b66a9f918d4e161919cd4301ab768f4aaf5526f7b7ed43d02df30098 0.600000000000 1434962 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": 975003, "vin": [ { "gen": { "height": 974993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8988b741b66a9f918d4e161919cd4301ab768f4aaf5526f7b7ed43d02df30098" } } ], "extra": [ 1, 165, 115, 196, 224, 156, 10, 139, 215, 87, 221, 193, 193, 59, 192, 152, 64, 254, 85, 118, 167, 38, 203, 201, 168, 93, 192, 197, 231, 140, 16, 246, 158, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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