Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0b1bedb4ca759d679699a063056ea468dac073feb965aeaa459579813e18750

Tx prefix hash: 79c6c384ce171fffaf3fa07833681807e3ef3f1d850daed17019499ecd2d5809
Tx public key: 8e988b28e9d6d0ceca2094721dd5f0abea93115729b8b68c57d92e2e9559a461
Timestamp: 1581096605 Timestamp [UCT]: 2020-02-07 17:30:05 Age [y:d:h:m:s]: 04:325:17:13:50
Block: 60751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124207 RingCT/type: yes/0
Extra: 018e988b28e9d6d0ceca2094721dd5f0abea93115729b8b68c57d92e2e9559a46102110000000fd81c26c0000000000000000000

1 output(s) for total of 386.126885508000 dcy

stealth address amount amount idx
00: d6ea1af18484fbd2e1b0a359671b0eda8b645540683d9487874a8bd39b667a90 386.126885508000 111856 of 0

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": 60761, "vin": [ { "gen": { "height": 60751 } } ], "vout": [ { "amount": 386126885508, "target": { "key": "d6ea1af18484fbd2e1b0a359671b0eda8b645540683d9487874a8bd39b667a90" } } ], "extra": [ 1, 142, 152, 139, 40, 233, 214, 208, 206, 202, 32, 148, 114, 29, 213, 240, 171, 234, 147, 17, 87, 41, 184, 182, 140, 87, 217, 46, 46, 149, 89, 164, 97, 2, 17, 0, 0, 0, 15, 216, 28, 38, 192, 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