← previous blocknext block →recent activity
Analyzing
Block #87,621,983
22 transactions · 17 stateful · 2026-07-14 03:47:28 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,621,983 · 22 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
6w08w19w210w312w414w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5379ea4…bc3f
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x394020c6…fb55
0x34b655…2a6f
4 touches
1 conflict
0x52010f20…7082
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7138c945…f6a8
0x34b655…2a6f
4 touches
1 conflict
0x71806e15…2893
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 0xf5379ea492…8ebc3f
Audit this contract →
← previous block·next block →recent activity