Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64890b882b80c9c6543d67b54e8814ff2305ed793ec4a32b64be3e72971dade

Tx prefix hash: 4256eed971a057988f4fc13f0faca32c17b48076ca4bd7d49570c93ad39528e5
Tx public key: 3bba49d7f15bf6a8bff8d86bfa9d6f01219c0e34448f5677f35cd54ee5f8add6
Timestamp: 1608538254 Timestamp [UCT]: 2020-12-21 08:10:54 Age [y:d:h:m:s]: 04:008:00:30:21
Block: 166322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1018575 RingCT/type: yes/0
Extra: 013bba49d7f15bf6a8bff8d86bfa9d6f01219c0e34448f5677f35cd54ee5f8add6021100000369aad74b3a000000000000000000

1 output(s) for total of 172.550853070000 dcy

stealth address amount amount idx
00: c6a5f7a2d5c08d2166fcb1d68fcc019e5d95f96fd313232fc063a10657f906a4 172.550853070000 304371 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": 166332, "vin": [ { "gen": { "height": 166322 } } ], "vout": [ { "amount": 172550853070, "target": { "key": "c6a5f7a2d5c08d2166fcb1d68fcc019e5d95f96fd313232fc063a10657f906a4" } } ], "extra": [ 1, 59, 186, 73, 215, 241, 91, 246, 168, 191, 248, 216, 107, 250, 157, 111, 1, 33, 156, 14, 52, 68, 143, 86, 119, 243, 92, 213, 78, 229, 248, 173, 214, 2, 17, 0, 0, 3, 105, 170, 215, 75, 58, 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