Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe6ef89f2369a75e091ceb165bddd574b638356ab4f62812edd51161b7d26e0e

Tx prefix hash: 8eb50b17b54875e1138853b43443a4657ee27449ae471638995a7e752b859832
Tx public key: 5b8b71871325a03351f3977243ec2cbae7ca0b4809c8a1e34b2f9288c29c15ae
Timestamp: 1625584235 Timestamp [UCT]: 2021-07-06 15:10:35 Age [y:d:h:m:s]: 03:124:13:34:09
Block: 289230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 859055 RingCT/type: yes/0
Extra: 015b8b71871325a03351f3977243ec2cbae7ca0b4809c8a1e34b2f9288c29c15ae02110000002d694a138f000000000000000000

1 output(s) for total of 67.555614876000 dcy

stealth address amount amount idx
00: 3dcceda1ace5a712c1ace324e0b3c03c7f031fa4d55e59e7deb576aec22e7135 67.555614876000 605823 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": 289240, "vin": [ { "gen": { "height": 289230 } } ], "vout": [ { "amount": 67555614876, "target": { "key": "3dcceda1ace5a712c1ace324e0b3c03c7f031fa4d55e59e7deb576aec22e7135" } } ], "extra": [ 1, 91, 139, 113, 135, 19, 37, 160, 51, 81, 243, 151, 114, 67, 236, 44, 186, 231, 202, 11, 72, 9, 200, 161, 227, 75, 47, 146, 136, 194, 156, 21, 174, 2, 17, 0, 0, 0, 45, 105, 74, 19, 143, 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