Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec983c7b603d46573e862d6477fc2c9a21cc1b4d655c6f9a72bbdf5d99431273

Tx prefix hash: 4cf4fbde36417687ad4d63dce0000d3212ff927043e2e957cdf34c951b37abe3
Tx public key: e9c52b2fda9b742344648cbb5dffedde7774b732aaa20ff26892fa7e3a5ca8a8
Timestamp: 1706950504 Timestamp [UCT]: 2024-02-03 08:55:04 Age [y:d:h:m:s]: 00:347:13:45:03
Block: 949353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248829 RingCT/type: yes/0
Extra: 01e9c52b2fda9b742344648cbb5dffedde7774b732aaa20ff26892fa7e3a5ca8a802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 198780f2d7a5e3a3c9301783b9a51e91257f34294802f0244cb6886b3bfc260c 0.600000000000 1407877 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": 949363, "vin": [ { "gen": { "height": 949353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "198780f2d7a5e3a3c9301783b9a51e91257f34294802f0244cb6886b3bfc260c" } } ], "extra": [ 1, 233, 197, 43, 47, 218, 155, 116, 35, 68, 100, 140, 187, 93, 255, 237, 222, 119, 116, 183, 50, 170, 162, 15, 242, 104, 146, 250, 126, 58, 92, 168, 168, 2, 17, 0, 0, 0, 4, 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