Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2ef2031e56382ca66992773c0cf9f30ca0e516d7fa48ca203310d45416b2a3e

Tx prefix hash: b6e527af489907224eca09dd1ec5c5f818c12911659aeb527910a4c9ddbbaa81
Tx public key: 792c9b473d6acd040bb99c5137c1773a46c820c3a253a05a0f6e0148affadbf0
Timestamp: 1649266587 Timestamp [UCT]: 2022-04-06 17:36:27 Age [y:d:h:m:s]: 02:264:14:44:13
Block: 474565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708896 RingCT/type: yes/0
Extra: 01792c9b473d6acd040bb99c5137c1773a46c820c3a253a05a0f6e0148affadbf0021100000001bf7ee4e7000000000000000000

1 output(s) for total of 16.427421346000 dcy

stealth address amount amount idx
00: 100088f61f2bc8306e0a179cbf4921903c95a0928e71ed33159d69b79dfc49c8 16.427421346000 894632 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": 474575, "vin": [ { "gen": { "height": 474565 } } ], "vout": [ { "amount": 16427421346, "target": { "key": "100088f61f2bc8306e0a179cbf4921903c95a0928e71ed33159d69b79dfc49c8" } } ], "extra": [ 1, 121, 44, 155, 71, 61, 106, 205, 4, 11, 185, 156, 81, 55, 193, 119, 58, 70, 200, 32, 195, 162, 83, 160, 90, 15, 110, 1, 72, 175, 250, 219, 240, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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