Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c974fc3a0861457a56241f757a659d0b214c93b2736fa5b5e686ffc17b88bd3e

Tx prefix hash: 15bf4db39f04822a0b0c087d19491e1a3a2333f88270f84bbabb3ac92291c897
Tx public key: 8aef30253993fa6740735f6f11a2240b047babe0e42388b17b26611db31a579f
Timestamp: 1706430710 Timestamp [UCT]: 2024-01-28 08:31:50 Age [y:d:h:m:s]: 01:070:09:59:49
Block: 945034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311406 RingCT/type: yes/0
Extra: 018aef30253993fa6740735f6f11a2240b047babe0e42388b17b26611db31a579f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1d5d266d85a600e07e0902a729c1c49b749a86a41372eb9b5cb759b243feb23 0.600000000000 1403342 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": 945044, "vin": [ { "gen": { "height": 945034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1d5d266d85a600e07e0902a729c1c49b749a86a41372eb9b5cb759b243feb23" } } ], "extra": [ 1, 138, 239, 48, 37, 57, 147, 250, 103, 64, 115, 95, 111, 17, 162, 36, 11, 4, 123, 171, 224, 228, 35, 136, 177, 123, 38, 97, 29, 179, 26, 87, 159, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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