← previous blocknext block →recent activity
Analyzing
Block #87,734,870
18 transactions · 16 stateful · 2026-07-14 16:22:33 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,734,870 · 18 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
1w02w13w07w18w29w310w215w016w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5b9e5ecc…2bc7
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xcf5ef070…7d4f
0x34b655…2a6f
6 touches
3 conflicts
0x0eb1245e…cdd1
0x34b655…2a6f
4 touches
1 conflict
0x2f35c56f…046b
0x34b655…2a6f
4 touches
1 conflict
0x40883ce5…2ae2
0x34b655…2a6f
4 touches
1 conflict
0x426e1f22…5ff9
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity