Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee9ed568ef0a7a6e2c9b2ba9b98f53cd99ee6a22d44638b0c43de4b612128659

Tx prefix hash: a92f4c3451906a944dfaea8138234f84fc75c5e76af999da3417e3ff3338b172
Tx public key: cd2bd43f886e89a5fef9fd3dd9e8372a4b63a38183fe942b3bfcefa3d245853d
Timestamp: 1653378939 Timestamp [UCT]: 2022-05-24 07:55:39 Age [y:d:h:m:s]: 02:229:06:06:27
Block: 507750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 684461 RingCT/type: yes/0
Extra: 01cd2bd43f886e89a5fef9fd3dd9e8372a4b63a38183fe942b3bfcefa3d245853d021100000001cb8520c2000000000000000000

1 output(s) for total of 12.753038393000 dcy

stealth address amount amount idx
00: 8a575596ff343470d7a68e350124266a1c26f3a635f38cd724527954da966fec 12.753038393000 933553 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": 507760, "vin": [ { "gen": { "height": 507750 } } ], "vout": [ { "amount": 12753038393, "target": { "key": "8a575596ff343470d7a68e350124266a1c26f3a635f38cd724527954da966fec" } } ], "extra": [ 1, 205, 43, 212, 63, 136, 110, 137, 165, 254, 249, 253, 61, 217, 232, 55, 42, 75, 99, 163, 129, 131, 254, 148, 43, 59, 252, 239, 163, 210, 69, 133, 61, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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