← previous blocknext block →recent activity
Analyzing
Block #87,871,812
27 transactions · 23 stateful · 2026-07-15 07:38:33 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,871,812 · 27 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
2w08w09w110w213w115w217w120w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0xfa551be3…a911
0xa6afd3…d132
4 touches
1 conflict
0xbcc65f18…4231
0x34b655…2a6f
4 touches
1 conflict
0xd4ccd78c…8309
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdd5c7a1c…cecb
0x34b655…2a6f
4 touches
1 conflict
0xfe2c1082…db16
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity