Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 936f5bb4181051e443a92da62f6a1a8334d9257535185efbb8de3aa1cad96d32

Tx prefix hash: 66847b9a024e338d12e0ae94ae2fbb71b4a07b0291103b4c6633b2ad0b361e3b
Tx public key: c007bcb7a9c6c1aaaee55f02103326987ad8c8efe13ce433c955d10ab7053f28
Timestamp: 1580891764 Timestamp [UCT]: 2020-02-05 08:36:04 Age [y:d:h:m:s]: 05:118:16:04:39
Block: 59166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1236830 RingCT/type: yes/0
Extra: 01c007bcb7a9c6c1aaaee55f02103326987ad8c8efe13ce433c955d10ab7053f280211000000024943cd9f000000000000000000

1 output(s) for total of 390.811020291000 dcy

stealth address amount amount idx
00: e735e5f39c60caa982fa079684e51b2d26934d917b7d885bb3791487f4df1498 390.811020291000 109206 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": 59176, "vin": [ { "gen": { "height": 59166 } } ], "vout": [ { "amount": 390811020291, "target": { "key": "e735e5f39c60caa982fa079684e51b2d26934d917b7d885bb3791487f4df1498" } } ], "extra": [ 1, 192, 7, 188, 183, 169, 198, 193, 170, 174, 229, 95, 2, 16, 51, 38, 152, 122, 216, 200, 239, 225, 60, 228, 51, 201, 85, 209, 10, 183, 5, 63, 40, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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