Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b090262662f0a32f0c2267554753feb4114e07890a32de9b17541e5324c82fc

Tx prefix hash: 4ef7bcb79ef55ff6c8dd5e8deae79aea344a49700b7cb213c3c3b2fb6e988e81
Tx public key: a0bb5fcaeda43414be3d22e97427498f533b186cdc5e0d56c917adace4e7610b
Timestamp: 1576424616 Timestamp [UCT]: 2019-12-15 15:43:36 Age [y:d:h:m:s]: 04:339:03:34:06
Block: 27441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128438 RingCT/type: yes/0
Extra: 01a0bb5fcaeda43414be3d22e97427498f533b186cdc5e0d56c917adace4e7610b0211000000479159db1e000000000000000000

1 output(s) for total of 497.825847468000 dcy

stealth address amount amount idx
00: bbc569b2b786e64cee223bf89128e8bf23307cec586417bb20599260783b2f74 497.825847468000 45441 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": 27451, "vin": [ { "gen": { "height": 27441 } } ], "vout": [ { "amount": 497825847468, "target": { "key": "bbc569b2b786e64cee223bf89128e8bf23307cec586417bb20599260783b2f74" } } ], "extra": [ 1, 160, 187, 95, 202, 237, 164, 52, 20, 190, 61, 34, 233, 116, 39, 73, 143, 83, 59, 24, 108, 220, 94, 13, 86, 201, 23, 173, 172, 228, 231, 97, 11, 2, 17, 0, 0, 0, 71, 145, 89, 219, 30, 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