Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbdc5edeb1ef092d0052f533d76ce78b8251ad404d0dafe997cae6fbc28df434

Tx prefix hash: a686863bac29c1757dc4bffd9c61c2671f3912f10f447b3ff931ecc39b8b3e70
Tx public key: c697423dfd87ed9ad650628fad7cb9dc05046a26fe02e3eacf1b729832372fe5
Timestamp: 1705463018 Timestamp [UCT]: 2024-01-17 03:43:38 Age [y:d:h:m:s]: 01:119:00:23:00
Block: 937004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346197 RingCT/type: yes/0
Extra: 01c697423dfd87ed9ad650628fad7cb9dc05046a26fe02e3eacf1b729832372fe502110000000182025268000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dced29b447da0a901021d82f3e57e677d8a474cb08fd802e1c36871efd47184e 0.600000000000 1395048 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": 937014, "vin": [ { "gen": { "height": 937004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dced29b447da0a901021d82f3e57e677d8a474cb08fd802e1c36871efd47184e" } } ], "extra": [ 1, 198, 151, 66, 61, 253, 135, 237, 154, 214, 80, 98, 143, 173, 124, 185, 220, 5, 4, 106, 38, 254, 2, 227, 234, 207, 27, 114, 152, 50, 55, 47, 229, 2, 17, 0, 0, 0, 1, 130, 2, 82, 104, 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