Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f753ef62f515d99742d83e297278bca40fa71c8ea518bcad3d0d651a07a1047e

Tx prefix hash: c73868e8846e84120d3c6d9a4ff24225c7d6941721be9809215bdb625421f32e
Tx public key: ae8b11fe28e5f508b21e75e70cd84450de91562c650d353db6c7b72f330c2f75
Timestamp: 1725207312 Timestamp [UCT]: 2024-09-01 16:15:12 Age [y:d:h:m:s]: 00:228:18:10:53
Block: 1100729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163351 RingCT/type: yes/0
Extra: 01ae8b11fe28e5f508b21e75e70cd84450de91562c650d353db6c7b72f330c2f7502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cc6cd04d7b4e9cad9f9f0eab3385c94e8555bade33c2b3bebeec51e6fc65475 0.600000000000 1576710 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": 1100739, "vin": [ { "gen": { "height": 1100729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cc6cd04d7b4e9cad9f9f0eab3385c94e8555bade33c2b3bebeec51e6fc65475" } } ], "extra": [ 1, 174, 139, 17, 254, 40, 229, 245, 8, 178, 30, 117, 231, 12, 216, 68, 80, 222, 145, 86, 44, 101, 13, 53, 61, 182, 199, 183, 47, 51, 12, 47, 117, 2, 17, 0, 0, 0, 12, 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