Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feac72d0660f739b02bbb3a7d548f01b37a0aad9450fbb0fff57ee5168c512f9

Tx prefix hash: 05bd9c73d333e64f418c38b2ec27a60b8d74e9aec0a7334edf07f6b016b68c9e
Tx public key: d2279b445614e70307f3ce9e2500759100f71b76d0fd68ffa5cd886e213a0008
Timestamp: 1720595930 Timestamp [UCT]: 2024-07-10 07:18:50 Age [y:d:h:m:s]: 01:124:12:19:25
Block: 1062505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347507 RingCT/type: yes/0
Extra: 01d2279b445614e70307f3ce9e2500759100f71b76d0fd68ffa5cd886e213a000802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21d7b3a4a46d70244d61605c1b012c773aed3b01401e8d3000383168655290d9 0.600000000000 1533008 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": 1062515, "vin": [ { "gen": { "height": 1062505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21d7b3a4a46d70244d61605c1b012c773aed3b01401e8d3000383168655290d9" } } ], "extra": [ 1, 210, 39, 155, 68, 86, 20, 231, 3, 7, 243, 206, 158, 37, 0, 117, 145, 0, 247, 27, 118, 208, 253, 104, 255, 165, 205, 136, 110, 33, 58, 0, 8, 2, 17, 0, 0, 0, 7, 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