← previous blocknext block →recent activity
Analyzing
Block #87,410,589
18 transactions · 17 stateful · 2026-07-13 04:13:03 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,410,589 · 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
2w03w07w18w29w311w413w014w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dc6cd61…f674
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x05a7428b…ddf3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbbedfd60…0fec
0x34b655…2a6f
4 touches
1 conflict
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0xd69f26b4…c204
0x2a68ba…90c5
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 0x4dc6cd6114…b6f674
Audit this contract →
← previous block·next block →recent activity