← previous blocknext block →recent activity
Analyzing
Block #87,314,172
31 transactions · 28 stateful · 2026-07-12 17:28:09 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,314,172 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w18w09w110w212w015w016w120w022w124w325w328w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4fbfa0e…694e
0x34b655…2a6f
8 touches
6 conflicts
0x0eac6378…36f4
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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 0xb4fbfa0e1e…23694e
Audit this contract →
← previous block·next block →recent activity