← previous blocknext block →recent activity
Analyzing
Block #87,253,241
16 transactions · 15 stateful · 2026-07-12 10:40:44 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,253,241 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w08w19w210w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b61269…48d7
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0xf2ab626b…5c5b
0x34b655…2a6f
4 touches
1 conflict
0x36a85feb…891b
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc6d563ee…1268
0x34b655…2a6f
4 touches
1 conflict
0xdb529f62…663c
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 0x38b61269d3…c048d7
Audit this contract →
← previous block·next block →recent activity