← previous blocknext block →recent activity
Analyzing
Block #87,454,518
13 transactions · 10 stateful · 2026-07-13 09:06:43 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,454,518 · 13 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
2w03w14w28w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x56f6adae…573c
0x34b655…2a6f
4 touches
1 conflict
0x0090639e…243e
0x34b655…2a6f
4 touches
1 conflict
0x6030bece…bf0e
0x34b655…2a6f
4 touches
1 conflict
0x2b4f426d…5de5
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity