Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d93b9875e9ec8989f8dc42d5309b382e833617451f785f58b1e513997f688309

Tx prefix hash: 984c7871acd8d9df920fa7d3b307fa5667ebbfd3578a9ac84bdd30db74bd89ed
Tx public key: 35ec5d1c51d1a0eaf5f13f6d65c0e352e3ac8486a8cf37d954ab7bbc2d2a07f4
Timestamp: 1575768710 Timestamp [UCT]: 2019-12-08 01:31:50 Age [y:d:h:m:s]: 05:039:16:41:23
Block: 22930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1174410 RingCT/type: yes/0
Extra: 0135ec5d1c51d1a0eaf5f13f6d65c0e352e3ac8486a8cf37d954ab7bbc2d2a07f4020d393030310002000000176e66db

1 output(s) for total of 515.257431109000 dcy

stealth address amount amount idx
00: fdb7fe8e8362d6d169cef8909ebd610afa850ca64a3bc0fb4520a54defe8692f 515.257431109000 36341 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": 22940, "vin": [ { "gen": { "height": 22930 } } ], "vout": [ { "amount": 515257431109, "target": { "key": "fdb7fe8e8362d6d169cef8909ebd610afa850ca64a3bc0fb4520a54defe8692f" } } ], "extra": [ 1, 53, 236, 93, 28, 81, 209, 160, 234, 245, 241, 63, 109, 101, 192, 227, 82, 227, 172, 132, 134, 168, 207, 55, 217, 84, 171, 123, 188, 45, 42, 7, 244, 2, 13, 57, 48, 48, 49, 0, 2, 0, 0, 0, 23, 110, 102, 219 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8