Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4f113090abb76364770ba42b9887baf4956df2251f53640b920e46c2a84b6d0

Tx prefix hash: 05019a845798209f9171db0d1ec664b3a836399ab91f62692b651a396812b12d
Tx public key: 93b1238e504cd995e86e95fdcae4fb5cec7394543b490c3815b0a32b4a9dc66c
Timestamp: 1719439284 Timestamp [UCT]: 2024-06-26 22:01:24 Age [y:d:h:m:s]: 00:263:13:15:35
Block: 1052901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188338 RingCT/type: yes/0
Extra: 0193b1238e504cd995e86e95fdcae4fb5cec7394543b490c3815b0a32b4a9dc66c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0d6c80a1ea86da9d55476b5bbf43144eae9f0c5473e81034174fc916f4ca651 0.600000000000 1523244 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": 1052911, "vin": [ { "gen": { "height": 1052901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0d6c80a1ea86da9d55476b5bbf43144eae9f0c5473e81034174fc916f4ca651" } } ], "extra": [ 1, 147, 177, 35, 142, 80, 76, 217, 149, 232, 110, 149, 253, 202, 228, 251, 92, 236, 115, 148, 84, 59, 73, 12, 56, 21, 176, 163, 43, 74, 157, 198, 108, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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