← previous blocknext block →recent activity
Analyzing
Block #86,799,903
21 transactions · 14 stateful · 2026-07-10 08:10:00 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,799,903 · 21 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
3w05w16w210w312w019w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6a8d7ce…d4f1
0x34b655…2a6f
6 touches
3 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x19caa5cc…17c7
0x34b655…2a6f
4 touches
1 conflict
0x26064b2b…62b5
0x34b655…2a6f
4 touches
1 conflict
0x356f8a28…5791
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64d353bf…54eb
0x34b655…2a6f
4 touches
1 conflict
0x64d353bf…54ec
0x34b655…2a6f
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 0xa6a8d7cec5…24d4f1
Audit this contract →
← previous block·next block →recent activity