Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d68e8b82b9b815d75bf313d5cbd0115675841b583850d0b6c5b5134b953aadce

Tx prefix hash: 1e5217436e23b861edabe9829ab5a58bd2d3ffd8936d70dde862b87df6864ea5
Tx public key: 962928ed9737c2c2db3e3b25ba6f0538d41c7c723140ad2fd327ba8bafc40aa2
Timestamp: 1714467601 Timestamp [UCT]: 2024-04-30 09:00:01 Age [y:d:h:m:s]: 01:191:21:49:15
Block: 1011686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395792 RingCT/type: yes/0
Extra: 01962928ed9737c2c2db3e3b25ba6f0538d41c7c723140ad2fd327ba8bafc40aa202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9800f87c16c92565129f3ce83ca84e030a211908e73c59fab93645e44a7d4e2 0.600000000000 1473980 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": 1011696, "vin": [ { "gen": { "height": 1011686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9800f87c16c92565129f3ce83ca84e030a211908e73c59fab93645e44a7d4e2" } } ], "extra": [ 1, 150, 41, 40, 237, 151, 55, 194, 194, 219, 62, 59, 37, 186, 111, 5, 56, 212, 28, 124, 114, 49, 64, 173, 47, 211, 39, 186, 139, 175, 196, 10, 162, 2, 17, 0, 0, 0, 3, 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