Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e7e3ee0fa99cf937bc8abf9a1c647043a130c69450d14029d8e861c8ad52f1

Tx prefix hash: d097b793044ff9127d2c29d7fc187a0432363863ef0945e39cf7b5271bf5bc1b
Tx public key: 071993927d07cc57f650a645242c2a9ec0a510d478209e0c15a8ac97086a4a00
Timestamp: 1707837469 Timestamp [UCT]: 2024-02-13 15:17:49 Age [y:d:h:m:s]: 01:052:18:19:48
Block: 956718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298750 RingCT/type: yes/0
Extra: 01071993927d07cc57f650a645242c2a9ec0a510d478209e0c15a8ac97086a4a0002110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b267de911356e8922c8a001eb357258e044b9df500aa8db56cb51a6d186a9a6 0.600000000000 1416028 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": 956728, "vin": [ { "gen": { "height": 956718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b267de911356e8922c8a001eb357258e044b9df500aa8db56cb51a6d186a9a6" } } ], "extra": [ 1, 7, 25, 147, 146, 125, 7, 204, 87, 246, 80, 166, 69, 36, 44, 42, 158, 192, 165, 16, 212, 120, 32, 158, 12, 21, 168, 172, 151, 8, 106, 74, 0, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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