← previous blocknext block →recent activity
Analyzing
Block #87,900,041
20 transactions · 19 stateful · 2026-07-15 10:47:23 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,900,041 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w18w29w210w313w014w415w416w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84585d11…6ae7
0x34b655…2a6f
8 touches
6 conflicts
0xe40c96f3…9ce4
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x5036f376…c06a
0x34b655…2a6f
4 touches
1 conflict
0x6d156df4…b643
0x34b655…2a6f
4 touches
1 conflict
0x765dc3f0…0be7
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
6 conflicts on slot 0x84585d11a1…0b6ae7
Audit this contract →
← previous block·next block →recent activity