Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3023a38eb9255e4d160fad9472bd613914ea885716e3adb1688ff7961fac041

Tx prefix hash: 42f5585a24800052f3470b8c20432fbe68f2441e3fd900d15aaaf8dfeb844b6a
Tx public key: caf9999e619933f7b9074c1edbe9dc972c6f8ea33416db523231f411ec78d476
Timestamp: 1693479698 Timestamp [UCT]: 2023-08-31 11:01:38 Age [y:d:h:m:s]: 01:076:15:56:09
Block: 837868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316080 RingCT/type: yes/0
Extra: 01caf9999e619933f7b9074c1edbe9dc972c6f8ea33416db523231f411ec78d4760211000000104b8f5122000000000000000000

1 output(s) for total of 1.027532518000 dcy

stealth address amount amount idx
00: 7fd7ce634d9ca0faa680ae8fdafb51549cdb2afb9b9ae7b338571b5a0867fe07 1.027532518000 1290542 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": 837878, "vin": [ { "gen": { "height": 837868 } } ], "vout": [ { "amount": 1027532518, "target": { "key": "7fd7ce634d9ca0faa680ae8fdafb51549cdb2afb9b9ae7b338571b5a0867fe07" } } ], "extra": [ 1, 202, 249, 153, 158, 97, 153, 51, 247, 185, 7, 76, 30, 219, 233, 220, 151, 44, 111, 142, 163, 52, 22, 219, 82, 50, 49, 244, 17, 236, 120, 212, 118, 2, 17, 0, 0, 0, 16, 75, 143, 81, 34, 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