Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0237c83066a82f066fd35d53dc1acf846d38bf8b8406e2847caa2f6a92ce262

Tx prefix hash: a56dfc399044481216ef6bf9e878612c94b731636818d711ac7fe7d4d1746dd3
Tx public key: 378e6f58d0d23e3a0f9aad1bfd8b615f1f8e10f453545a82fd65bf947bab35fb
Timestamp: 1657289951 Timestamp [UCT]: 2022-07-08 14:19:11 Age [y:d:h:m:s]: 02:108:21:05:47
Block: 539371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599144 RingCT/type: yes/0
Extra: 01378e6f58d0d23e3a0f9aad1bfd8b615f1f8e10f453545a82fd65bf947bab35fb021100000002d3fcec30000000000000000000

1 output(s) for total of 10.019363230000 dcy

stealth address amount amount idx
00: 949c3e3ee3050406f2975725b895576d24d516d46901524897d2b5557fa7c4c6 10.019363230000 969466 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": 539381, "vin": [ { "gen": { "height": 539371 } } ], "vout": [ { "amount": 10019363230, "target": { "key": "949c3e3ee3050406f2975725b895576d24d516d46901524897d2b5557fa7c4c6" } } ], "extra": [ 1, 55, 142, 111, 88, 208, 210, 62, 58, 15, 154, 173, 27, 253, 139, 97, 95, 31, 142, 16, 244, 83, 84, 90, 130, 253, 101, 191, 148, 123, 171, 53, 251, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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