Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9de49869e8f5c30af695ff2e485c5a01d1a306b192f9db308e165f414d2e913

Tx prefix hash: 786f7fe970f5e9309ef33b2cec5ad99b4fc2f0608252ebf6fbb0603fa4a89104
Tx public key: f5ed1b82ed340fcfe91846a488238dbc86dbd91c905f12e9e2ba2820a420d079
Timestamp: 1733778946 Timestamp [UCT]: 2024-12-09 21:15:46 Age [y:d:h:m:s]: 00:120:17:38:29
Block: 1171694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86077 RingCT/type: yes/0
Extra: 01f5ed1b82ed340fcfe91846a488238dbc86dbd91c905f12e9e2ba2820a420d0790211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aceae773a25a8324d4e3e285c604ac9c1a1726806935b54da34e7fc5f7bcedf6 0.600000000000 1657485 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": 1171704, "vin": [ { "gen": { "height": 1171694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aceae773a25a8324d4e3e285c604ac9c1a1726806935b54da34e7fc5f7bcedf6" } } ], "extra": [ 1, 245, 237, 27, 130, 237, 52, 15, 207, 233, 24, 70, 164, 136, 35, 141, 188, 134, 219, 217, 28, 144, 95, 18, 233, 226, 186, 40, 32, 164, 32, 208, 121, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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