Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d2936d11502e5e2d6078e018770b8e85642db10623c81732856fa4f9d29ce5

Tx prefix hash: a9b613a130177dd937e043fcddea37449dfdd340152bdd3ac33e49e7e6881bac
Tx public key: 9774e84de24ee902529ad52d0480521c2c7f2af9b098d1c5aae9a6b0cbaa9382
Timestamp: 1718554715 Timestamp [UCT]: 2024-06-16 16:18:35 Age [y:d:h:m:s]: 00:277:05:40:49
Block: 1045593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198102 RingCT/type: yes/0
Extra: 019774e84de24ee902529ad52d0480521c2c7f2af9b098d1c5aae9a6b0cbaa938202110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6368d9e6a362c0d690df6d982efcc9a5f78b2cc6492274cd430680320d18190 0.600000000000 1515204 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": 1045603, "vin": [ { "gen": { "height": 1045593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6368d9e6a362c0d690df6d982efcc9a5f78b2cc6492274cd430680320d18190" } } ], "extra": [ 1, 151, 116, 232, 77, 226, 78, 233, 2, 82, 154, 213, 45, 4, 128, 82, 28, 44, 127, 42, 249, 176, 152, 209, 197, 170, 233, 166, 176, 203, 170, 147, 130, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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