← previous blocknext block →recent activity
Analyzing
Block #86,232,741
24 transactions · 21 stateful · 2026-07-07 16:58:17 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,232,741 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w012w116w017w118w219w320w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x207cc41e…57c6
0x34b655…2a6f
4 touches
1 conflict
0x4cac4195…0139
0x34b655…2a6f
4 touches
1 conflict
0x5e7da795…a150
0x34b655…2a6f
4 touches
1 conflict
0x65eb0c36…cd9d
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x94dabb65…43a3
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity