Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0937ed1de15309baa5c2f9e34778be824e76acd6138534412229cae82f95862

Tx prefix hash: 57816842b053bb11e1ae9e1fd039bfcf7b867abc01cacf353e6ffd73c6690256
Tx public key: 4050344784989f20b46bc2c10c8d9f28e321e026f9d3e556b8ea93f09c5e132e
Timestamp: 1722694427 Timestamp [UCT]: 2024-08-03 14:13:47 Age [y:d:h:m:s]: 00:254:06:16:01
Block: 1079884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181635 RingCT/type: yes/0
Extra: 014050344784989f20b46bc2c10c8d9f28e321e026f9d3e556b8ea93f09c5e132e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b39dfbbcce1d2cdd960937fab503924cd9a3d794311e2f52d1c7d895ce9ca0b 0.600000000000 1553033 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": 1079894, "vin": [ { "gen": { "height": 1079884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b39dfbbcce1d2cdd960937fab503924cd9a3d794311e2f52d1c7d895ce9ca0b" } } ], "extra": [ 1, 64, 80, 52, 71, 132, 152, 159, 32, 180, 107, 194, 193, 12, 141, 159, 40, 227, 33, 224, 38, 249, 211, 229, 86, 184, 234, 147, 240, 156, 94, 19, 46, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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