← previous blocknext block →recent activity
Analyzing
Block #86,356,067
34 transactions · 30 stateful · 2026-07-08 06:41:49 UTC
Parallelism
88/100
Blocked
37%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,356,067 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w28w013w014w117w118w220w225w226w127w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a8cd0c…27bd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0x16a8cd0cae…8827bd
Audit this contract →
← previous block·next block →recent activity