Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be0f2d2f7168b6e69e5fd37ef4d0caee6fbb4ccee6707f8149f8cc8bd0ffb0b

Tx prefix hash: e17a2789c46f6881518609528627adb4d42a2394686b2c21daaf52640e03d6af
Tx public key: 8715850f8202f3c4c617f09b89cb95274edb2685e8b7ff8244baa6d97a7b1cb5
Timestamp: 1733155875 Timestamp [UCT]: 2024-12-02 16:11:15 Age [y:d:h:m:s]: 00:123:07:00:57
Block: 1166521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87921 RingCT/type: yes/0
Extra: 018715850f8202f3c4c617f09b89cb95274edb2685e8b7ff8244baa6d97a7b1cb5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4e14d97e7720d40d3a692dde9a47d160a2942a12e369b84c426ac4e2da1ae28 0.600000000000 1652208 of 15

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": 1166531, "vin": [ { "gen": { "height": 1166521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e14d97e7720d40d3a692dde9a47d160a2942a12e369b84c426ac4e2da1ae28" } } ], "extra": [ 1, 135, 21, 133, 15, 130, 2, 243, 196, 198, 23, 240, 155, 137, 203, 149, 39, 78, 219, 38, 133, 232, 183, 255, 130, 68, 186, 166, 217, 122, 123, 28, 181, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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