Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a2b31fdf56b36efd9ad68328ef5a6a29711c22811307b34d94ba879f0dd3345

Tx prefix hash: a9b9e947aa521d6e8eaf0baa499b735f0691b832d0fe0080a5a5ff29061ed705
Tx public key: 57cafb73332878ec1a37d77079a312cc7f28504169dce6b18394784259fd60f6
Timestamp: 1577431665 Timestamp [UCT]: 2019-12-27 07:27:45 Age [y:d:h:m:s]: 04:338:14:56:06
Block: 32728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131110 RingCT/type: yes/0
Extra: 0157cafb73332878ec1a37d77079a312cc7f28504169dce6b18394784259fd60f602110000000cd81c26c0000000000000000000

1 output(s) for total of 478.144768317000 dcy

stealth address amount amount idx
00: d1459f3cedb4a3b5326645d48535c9d28b826677891dd0c1b6b27b7618eaf65a 478.144768317000 54511 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": 32738, "vin": [ { "gen": { "height": 32728 } } ], "vout": [ { "amount": 478144768317, "target": { "key": "d1459f3cedb4a3b5326645d48535c9d28b826677891dd0c1b6b27b7618eaf65a" } } ], "extra": [ 1, 87, 202, 251, 115, 51, 40, 120, 236, 26, 55, 215, 112, 121, 163, 18, 204, 127, 40, 80, 65, 105, 220, 230, 177, 131, 148, 120, 66, 89, 253, 96, 246, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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