Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd43ed09907918a144d732bc0f832d38928e14a476e49b9b29d07b0c91c55e02

Tx prefix hash: 1f1ed6e74eee22dc1cd7df798c34b719d56172f2f9b9f07a714c6da405d31f4a
Tx public key: ecada8ee2b34bb3aecb703d94b83f8ca08cee41020cc27cf408cca28c48c8a83
Timestamp: 1728205726 Timestamp [UCT]: 2024-10-06 09:08:46 Age [y:d:h:m:s]: 00:169:16:10:56
Block: 1125594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121042 RingCT/type: yes/0
Extra: 01ecada8ee2b34bb3aecb703d94b83f8ca08cee41020cc27cf408cca28c48c8a8302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa1bbee32b8af7952927920c9e154e5724abc1909930fd26da1d722ce4bb55a7 0.600000000000 1608345 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": 1125604, "vin": [ { "gen": { "height": 1125594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa1bbee32b8af7952927920c9e154e5724abc1909930fd26da1d722ce4bb55a7" } } ], "extra": [ 1, 236, 173, 168, 238, 43, 52, 187, 58, 236, 183, 3, 217, 75, 131, 248, 202, 8, 206, 228, 16, 32, 204, 39, 207, 64, 140, 202, 40, 196, 140, 138, 131, 2, 17, 0, 0, 0, 2, 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