← previous blocknext block →recent activity
Analyzing
Block #87,903,788
19 transactions · 17 stateful · 2026-07-15 11:12:26 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,903,788 · 19 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
1w02w14w05w16w27w38w09w110w211w313w217w018w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x461a3556…5948
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x6aceb34c…8086
0x34b655…2a6f
4 touches
1 conflict
0x78b193e9…9c37
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 0x461a3556a1…3b5948
Audit this contract →
← previous block·next block →recent activity