Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b053c1162e6582f96da4c66b82e1037ee20ecfd13183929bff5f03d65f953538

Tx prefix hash: 73351ee1b557ce227fbc60f6a74c53ed613fae88ff52e60afdb3d8abb65742c8
Tx public key: 57ebba7998c5c4eac30a79d5e09e89fd0e34b305395abf6d3e08a5835402acc3
Timestamp: 1725946019 Timestamp [UCT]: 2024-09-10 05:26:59 Age [y:d:h:m:s]: 01:059:05:22:56
Block: 1106853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300741 RingCT/type: yes/0
Extra: 0157ebba7998c5c4eac30a79d5e09e89fd0e34b305395abf6d3e08a5835402acc3021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d276da22d8d33efcc9bb15ab45dadd4ffb10e0210e863f173c85574fbd7ed1d4 0.600000000000 1584454 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": 1106863, "vin": [ { "gen": { "height": 1106853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d276da22d8d33efcc9bb15ab45dadd4ffb10e0210e863f173c85574fbd7ed1d4" } } ], "extra": [ 1, 87, 235, 186, 121, 152, 197, 196, 234, 195, 10, 121, 213, 224, 158, 137, 253, 14, 52, 179, 5, 57, 90, 191, 109, 62, 8, 165, 131, 84, 2, 172, 195, 2, 17, 0, 0, 0, 7, 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