Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557e53799bc1fa93757f114d9b1635025f9b616d88a4aa1ae22ac996d48758d7

Tx prefix hash: ff78f6db5b1ccdcb1f405c5ed41a61e13b4c1bbd83508aa6f1ba5dd3f4f9de54
Tx public key: 7772b49acd54875845de822eb283b06d5c22971cff45ff35eca647340c4d6473
Timestamp: 1722211004 Timestamp [UCT]: 2024-07-28 23:56:44 Age [y:d:h:m:s]: 00:232:10:05:22
Block: 1075879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166028 RingCT/type: yes/0
Extra: 017772b49acd54875845de822eb283b06d5c22971cff45ff35eca647340c4d647302110000001391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f73d779fe5ef3ae63b7ef08fab8fe75ca03c833a4dc1008fd47e665a5c5c286 0.600000000000 1548410 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": 1075889, "vin": [ { "gen": { "height": 1075879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f73d779fe5ef3ae63b7ef08fab8fe75ca03c833a4dc1008fd47e665a5c5c286" } } ], "extra": [ 1, 119, 114, 180, 154, 205, 84, 135, 88, 69, 222, 130, 46, 178, 131, 176, 109, 92, 34, 151, 28, 255, 69, 255, 53, 236, 166, 71, 52, 12, 77, 100, 115, 2, 17, 0, 0, 0, 19, 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