← previous blocknext block →recent activity
Analyzing
Block #86,702,220
18 transactions · 15 stateful · 2026-07-09 21:17:36 UTC
Parallelism
89/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,702,220 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfab1627b…b819
0x34b655…2a6f
4 touches
1 conflict
0xb25fa8e2…c9ef
0x34b655…2a6f
4 touches
1 conflict
0xd1a8b9bd…6f8c
0x34b655…2a6f
4 touches
1 conflict
0xd4c35c53…39ab
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5e1db56…1d1a
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x05f9402d…cf20
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
1 conflict on slot 0xfab1627b61…32b819
Audit this contract →
← previous block·next block →recent activity