← previous blocknext block →recent activity
Analyzing
Block #87,662,910
18 transactions · 16 stateful · 2026-07-14 08:21:00 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,662,910 · 18 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
2w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x0bb92436…2eef
0x34b655…2a6f
2 touches
0 conflicts
0x0bce8fb9…edb6
0x34b655…2a6f
2 touches
0 conflicts
0x0e403c18…eac8
0x34b655…2a6f
2 touches
0 conflicts
0x17f75dcb…ab0c
0x34b655…2a6f
2 touches
0 conflicts
0x1a6cdc0e…0af5
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 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity