Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 918f91c5b2800ae4f345420a103be2b218de1d2d569df85c6bdc233a00859b21

Tx prefix hash: a4e25aefebc71c81112274bf442df419c6455582bcd57e976d268e25e845e5e3
Tx public key: ad9d571cd94c6950c63068bf3e6a54787fb0367a58af2643a26d5b0c2351459a
Timestamp: 1737216610 Timestamp [UCT]: 2025-01-18 16:10:10 Age [y:d:h:m:s]: 00:151:08:11:13
Block: 1200110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107896 RingCT/type: yes/0
Extra: 01ad9d571cd94c6950c63068bf3e6a54787fb0367a58af2643a26d5b0c2351459a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd372e34ece8dcb569dbefac6d61f7b932d5ce31b48cec5dcd022f91caf1396f 0.600000000000 1686751 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": 1200120, "vin": [ { "gen": { "height": 1200110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd372e34ece8dcb569dbefac6d61f7b932d5ce31b48cec5dcd022f91caf1396f" } } ], "extra": [ 1, 173, 157, 87, 28, 217, 76, 105, 80, 198, 48, 104, 191, 62, 106, 84, 120, 127, 176, 54, 122, 88, 175, 38, 67, 162, 109, 91, 12, 35, 81, 69, 154, 2, 17, 0, 0, 0, 5, 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