← previous blocknext block →recent activity
Analyzing
Block #87,754,108
19 transactions · 18 stateful · 2026-07-14 18:31:15 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,754,108 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w310w111w413w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebd124cf…589f
0x34b655…2a6f
8 touches
6 conflicts
0xa80684c9…3948
0x34b655…2a6f
6 touches
3 conflicts
0x644919d7…9727
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x709b98ea…4187
0x34b655…2a6f
4 touches
1 conflict
0x70b90757…51be
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 0xebd124cfb4…43589f
Audit this contract →
← previous block·next block →recent activity