← previous blocknext block →recent activity
Analyzing
Block #86,288,401
9 transactions · 6 stateful · 2026-07-07 23:09:52 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,288,401 · 9 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
4w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x002dfab7…aa48
0x34b655…2a6f
6 touches
3 conflicts
0x1e9dac68…ef8d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf6009797…7f5b
0x34b655…2a6f
6 touches
3 conflicts
0x2d9fe12d…54f4
0x34b655…2a6f
4 touches
1 conflict
0x3238e64a…5035
0x34b655…2a6f
4 touches
1 conflict
0x3581107a…a589
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 0xd99b3b6441…7a1c95
Audit this contract →
← previous block·next block →recent activity