Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f955e1f4921185c6131b23ad84022ff3cdd5db41fa8a548cbea8b9d883222e8

Tx prefix hash: ec6680c7aae740596b89811c2af5e475a4488a42f52cb6f8aee8a27dadca995b
Tx public key: c96dc16337f86edb41d8f90c21f10559966c9361f0203548e566375f3cb02945
Timestamp: 1627947003 Timestamp [UCT]: 2021-08-02 23:30:03 Age [y:d:h:m:s]: 03:146:22:03:26
Block: 306173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877675 RingCT/type: yes/0
Extra: 01c96dc16337f86edb41d8f90c21f10559966c9361f0203548e566375f3cb0294502110000001317696b73000000000000000000

1 output(s) for total of 59.363873914000 dcy

stealth address amount amount idx
00: 044fa679d1b81982c4e62bdd28cf67caa4fb547d76d16ed7de9c76e6d5694ea0 59.363873914000 638506 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": 306183, "vin": [ { "gen": { "height": 306173 } } ], "vout": [ { "amount": 59363873914, "target": { "key": "044fa679d1b81982c4e62bdd28cf67caa4fb547d76d16ed7de9c76e6d5694ea0" } } ], "extra": [ 1, 201, 109, 193, 99, 55, 248, 110, 219, 65, 216, 249, 12, 33, 241, 5, 89, 150, 108, 147, 97, 240, 32, 53, 72, 229, 102, 55, 95, 60, 176, 41, 69, 2, 17, 0, 0, 0, 19, 23, 105, 107, 115, 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