Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4579a750a6d8afac305d3d33f93e8a4a4bce79d0df7c3265d46c54ec73a410a0

Tx prefix hash: f2089e16688638c2c9a49d7d91c9ad43f4a260bd988d7ea924fb301d497f20aa
Tx public key: 82ce6b1d81c976691ab89f7009d07f73bdc0a27745c34ac271f2a475a5040460
Timestamp: 1696825781 Timestamp [UCT]: 2023-10-09 04:29:41 Age [y:d:h:m:s]: 01:215:09:50:43
Block: 865644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415003 RingCT/type: yes/0
Extra: 0182ce6b1d81c976691ab89f7009d07f73bdc0a27745c34ac271f2a475a504046002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.831308298000 dcy

stealth address amount amount idx
00: 65affbc429b1f25a10090303c9ac20db6d1a78fbce8ebea00aed57b227f47224 0.831308298000 1320182 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": 865654, "vin": [ { "gen": { "height": 865644 } } ], "vout": [ { "amount": 831308298, "target": { "key": "65affbc429b1f25a10090303c9ac20db6d1a78fbce8ebea00aed57b227f47224" } } ], "extra": [ 1, 130, 206, 107, 29, 129, 201, 118, 105, 26, 184, 159, 112, 9, 208, 127, 115, 189, 192, 162, 119, 69, 195, 74, 194, 113, 242, 164, 117, 165, 4, 4, 96, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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