← previous blocknext block →recent activity
Analyzing
Block #87,135,454
16 transactions · 15 stateful · 2026-07-11 21:32:25 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,135,454 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5ab2f5b…092b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x03faff26…f533
0x34b655…2a6f
4 touches
1 conflict
0x3bffe642…cff3
0x34b655…2a6f
4 touches
1 conflict
0x4c623175…29e4
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x796488e2…ee71
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 0xd5ab2f5bc4…1b092b
Audit this contract →
← previous block·next block →recent activity