← previous blocknext block →recent activity
Analyzing
Block #87,408,258
15 transactions · 14 stateful · 2026-07-13 03:57:24 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,408,258 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w19w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a1
0x34b655…2a6f
4 touches
1 conflict
0xc514314c…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xceb535f3…19cf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x276ed918…4bb5
0x34b655…2a6f
4 touches
1 conflict
0x0d2e1791…c1dd
0x34b655…2a6f
2 touches
0 conflicts
0x14b920f2…e214
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6b2ba712be…c40214
Audit this contract →
← previous block·next block →recent activity