Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05d698920abd916fe6900151b3da24cac646737c23e9a4252300304ffee983de

Tx prefix hash: 12e083f51e8805e2e9a226dde971da33369fb7359123820b4dcff4aa919ea8bd
Tx public key: dfe93b66e035f0a5fa635ecd998d53ef6acb6736add8f9ca034b27218dcbe809
Timestamp: 1722974143 Timestamp [UCT]: 2024-08-06 19:55:43 Age [y:d:h:m:s]: 00:290:08:36:15
Block: 1082212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207451 RingCT/type: yes/0
Extra: 01dfe93b66e035f0a5fa635ecd998d53ef6acb6736add8f9ca034b27218dcbe80902110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c61fc11309d123fe6ff903348e0d95d8dccb9335694cf6dc18505faf3c59a8e 0.600000000000 1556037 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": 1082222, "vin": [ { "gen": { "height": 1082212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c61fc11309d123fe6ff903348e0d95d8dccb9335694cf6dc18505faf3c59a8e" } } ], "extra": [ 1, 223, 233, 59, 102, 224, 53, 240, 165, 250, 99, 94, 205, 153, 141, 83, 239, 106, 203, 103, 54, 173, 216, 249, 202, 3, 75, 39, 33, 141, 203, 232, 9, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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