← previous blocknext block →recent activity
Analyzing
Block #86,044,971
18 transactions · 16 stateful · 2026-07-06 20:05:07 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
0.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,044,971 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w110w211w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7396f51…7f2f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x966e45cf…0f25
0x34b655…2a6f
6 touches
3 conflicts
0x9092da13…341b
0x34b655…2a6f
5 touches
3 conflicts
0x7b3f8378…b37d
0x34b655…2a6f
4 touches
1 conflict
0x8e507257…71c1
0x34b655…2a6f
4 touches
1 conflict
0xbe34553e…8485
0x34b655…2a6f
4 touches
1 conflict
0xd35315c0…5422
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
6 conflicts on slot 0xa7396f51b7…fd7f2f
Audit this contract →
← previous block·next block →recent activity