Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d4063bdee1670fc57bd6b49132f19ca5abf2d9f8290210292a3b0f67796ed8d

Tx prefix hash: 95f12ec0e57566235dd1c9ad4d851ccd81b9966b019f03c5791c7ba5e3cf78c7
Tx public key: 0307f3917dd1644c61c3ebf7bece454a6f595b92bfe6a737db983a4aa4de5423
Timestamp: 1735590208 Timestamp [UCT]: 2024-12-30 20:23:28 Age [y:d:h:m:s]: 00:168:20:22:09
Block: 1186671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120401 RingCT/type: yes/0
Extra: 010307f3917dd1644c61c3ebf7bece454a6f595b92bfe6a737db983a4aa4de5423021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6371c2d98794923a0b73af79223d146223015467d8a9fab4d2dd4982061b38e0 0.600000000000 1673156 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": 1186681, "vin": [ { "gen": { "height": 1186671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6371c2d98794923a0b73af79223d146223015467d8a9fab4d2dd4982061b38e0" } } ], "extra": [ 1, 3, 7, 243, 145, 125, 209, 100, 76, 97, 195, 235, 247, 190, 206, 69, 74, 111, 89, 91, 146, 191, 230, 167, 55, 219, 152, 58, 74, 164, 222, 84, 35, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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