Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1792cad70081c44fcfd77f3d798f351122ec3004cc570e1a5ad137766403fca

Tx prefix hash: 821f751d9e266f183a8778e400547d8cf6fbc8ccf0aec3632af07a56e31cd194
Tx public key: 62f1e7cc82e95dfca049c748a484e7de6cb14e3811c47fecdbc0c7ef12405eb4
Timestamp: 1720339928 Timestamp [UCT]: 2024-07-07 08:12:08 Age [y:d:h:m:s]: 00:186:19:57:01
Block: 1060377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133681 RingCT/type: yes/0
Extra: 0162f1e7cc82e95dfca049c748a484e7de6cb14e3811c47fecdbc0c7ef12405eb4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 899b74c0f2eea4e916add3960df491138d62146b3242f75bd44f397c57d6662b 0.600000000000 1530854 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": 1060387, "vin": [ { "gen": { "height": 1060377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "899b74c0f2eea4e916add3960df491138d62146b3242f75bd44f397c57d6662b" } } ], "extra": [ 1, 98, 241, 231, 204, 130, 233, 93, 252, 160, 73, 199, 72, 164, 132, 231, 222, 108, 177, 78, 56, 17, 196, 127, 236, 219, 192, 199, 239, 18, 64, 94, 180, 2, 17, 0, 0, 0, 4, 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