Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3144d702c51aa3e67d451ebf4648b61b8f2585cf9978413d2083734b0f41a44

Tx prefix hash: d3a8dcdb34f0b19c4b280015628cd7c39afe8eafe882710d90602c6dbe11b6df
Tx public key: ebe75625a6d26ec0d876cc44a1ccb28efb4b719fb0562c5b387377f75c6cf2dc
Timestamp: 1660966281 Timestamp [UCT]: 2022-08-20 03:31:21 Age [y:d:h:m:s]: 02:222:09:51:21
Block: 569684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 680169 RingCT/type: yes/0
Extra: 01ebe75625a6d26ec0d876cc44a1ccb28efb4b719fb0562c5b387377f75c6cf2dc021100000003ec6d1a1a000000000000000000

1 output(s) for total of 7.950611350000 dcy

stealth address amount amount idx
00: d548acecfdf28f243e3d8365f8f5a44f91e8415351b92c7cfe3d278db47bf76b 7.950611350000 1002841 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": 569694, "vin": [ { "gen": { "height": 569684 } } ], "vout": [ { "amount": 7950611350, "target": { "key": "d548acecfdf28f243e3d8365f8f5a44f91e8415351b92c7cfe3d278db47bf76b" } } ], "extra": [ 1, 235, 231, 86, 37, 166, 210, 110, 192, 216, 118, 204, 68, 161, 204, 178, 142, 251, 75, 113, 159, 176, 86, 44, 91, 56, 115, 119, 247, 92, 108, 242, 220, 2, 17, 0, 0, 0, 3, 236, 109, 26, 26, 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