← previous blocknext block →recent activity
Analyzing
Block #86,349,178
13 transactions · 12 stateful · 2026-07-08 05:55:48 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,349,178 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w17w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
6 touches
3 conflicts
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0xd8a63cf3…21cc
0x34b655…2a6f
5 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xa0f5612a…9804
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity