Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d1b60d0d7da091bef9deef21d0a3e94c2efd1df79e0de4deb831f93c49cbc98

Tx prefix hash: 9941c5c5d2f5af526439216993b502536ba9d004db4ec97171bc8b618b3229d8
Tx public key: ad00532d6bbe067f4c9695c21806a9317936f9ce31ec0a35f18018b5186b46e9
Timestamp: 1675626323 Timestamp [UCT]: 2023-02-05 19:45:23 Age [y:d:h:m:s]: 02:316:04:59:37
Block: 690555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745384 RingCT/type: yes/0
Extra: 01ad00532d6bbe067f4c9695c21806a9317936f9ce31ec0a35f18018b5186b46e9021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.161582719000 dcy

stealth address amount amount idx
00: 56fd0d0352f11ae48f7518a04d3cc0db34d0760505796eadf0ea7f3e2d1ef2f6 3.161582719000 1133285 of 0

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": 690565, "vin": [ { "gen": { "height": 690555 } } ], "vout": [ { "amount": 3161582719, "target": { "key": "56fd0d0352f11ae48f7518a04d3cc0db34d0760505796eadf0ea7f3e2d1ef2f6" } } ], "extra": [ 1, 173, 0, 83, 45, 107, 190, 6, 127, 76, 150, 149, 194, 24, 6, 169, 49, 121, 54, 249, 206, 49, 236, 10, 53, 241, 128, 24, 181, 24, 107, 70, 233, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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