Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199811caae17077e0c34e168cf03c62360e24fc3a0bb2ed92b262086a07fc53b

Tx prefix hash: b568770ab15a4a5d25af942cce2410ee74889f9b558ff307d792950451bff469
Tx public key: 2e67e81e2fb0d2250b92d6555d4fc1c5ab2b7913a713a8447a2071a418177a2a
Timestamp: 1581090539 Timestamp [UCT]: 2020-02-07 15:48:59 Age [y:d:h:m:s]: 05:003:08:51:37
Block: 60653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154507 RingCT/type: yes/0
Extra: 012e67e81e2fb0d2250b92d6555d4fc1c5ab2b7913a713a8447a2071a418177a2a0211000000030aca7173000000000000000000

1 output(s) for total of 386.395669204000 dcy

stealth address amount amount idx
00: 07dbc2d79c7f31b8819129401f096126aa02a6a240b76daf7c3edca476c3048b 386.395669204000 111686 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": 60663, "vin": [ { "gen": { "height": 60653 } } ], "vout": [ { "amount": 386395669204, "target": { "key": "07dbc2d79c7f31b8819129401f096126aa02a6a240b76daf7c3edca476c3048b" } } ], "extra": [ 1, 46, 103, 232, 30, 47, 176, 210, 37, 11, 146, 214, 85, 93, 79, 193, 197, 171, 43, 121, 19, 167, 19, 168, 68, 122, 32, 113, 164, 24, 23, 122, 42, 2, 17, 0, 0, 0, 3, 10, 202, 113, 115, 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