Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eb636524c0a2e604c597b8c691e0ef966b0ad86e7138827a20eef35571d5437

Tx prefix hash: ce56c5a70fb128b93db6e59c56f3a9dc177190b5f530a144a026abc2f1b961fb
Tx public key: 6cb5f245e0dd946dac3e1e2cfeeca57322a4ff577f5b55f61cccbbef84b8783b
Timestamp: 1582294650 Timestamp [UCT]: 2020-02-21 14:17:30 Age [y:d:h:m:s]: 05:123:05:54:34
Block: 69615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1241034 RingCT/type: yes/0
Extra: 016cb5f245e0dd946dac3e1e2cfeeca57322a4ff577f5b55f61cccbbef84b8783b02110000000203d36d11000000000000000000

1 output(s) for total of 360.858891481000 dcy

stealth address amount amount idx
00: 9f477b64c23d0f6d45615bc272dede61cb78d4f4eced0af477e79b9d3adad49c 360.858891481000 128382 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": 69625, "vin": [ { "gen": { "height": 69615 } } ], "vout": [ { "amount": 360858891481, "target": { "key": "9f477b64c23d0f6d45615bc272dede61cb78d4f4eced0af477e79b9d3adad49c" } } ], "extra": [ 1, 108, 181, 242, 69, 224, 221, 148, 109, 172, 62, 30, 44, 254, 236, 165, 115, 34, 164, 255, 87, 127, 91, 85, 246, 28, 204, 187, 239, 132, 184, 120, 59, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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