← previous blocknext block →recent activity
Analyzing
Block #87,319,716
17 transactions · 16 stateful · 2026-07-12 18:05:13 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,319,716 · 17 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
1w02w14w05w16w29w311w412w013w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94ba9c4a…41d8
0x34b655…2a6f
10 touches
10 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
8 touches
6 conflicts
0x6f95cc9f…e9b5
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x1ced2a7d…5c90
0x34b655…2a6f
6 touches
3 conflicts
0xe2c312f4…6eb6
0x34b655…2a6f
6 touches
3 conflicts
0xffdb3552…57ec
0x065c9d…c394
5 touches
3 conflicts
0x67db761a…4fa1
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
10 conflicts on slot 0x94ba9c4a07…0c41d8
Audit this contract →
← previous block·next block →recent activity