← previous blocknext block →recent activity
Analyzing
Block #87,496,510
21 transactions · 21 stateful · 2026-07-13 13:47:32 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,496,510 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w08w09w112w213w214w315w317w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ccf5c86…9954
0x851145…3f07
6 touches
3 conflicts
0xde696e46…6446
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x5610e3c2…be6f
0x34b655…2a6f
4 touches
1 conflict
0x5ecbbb8a…c1cd
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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: 0x851145ea…9f3f07
3 conflicts on slot 0x6ccf5c865d…b29954
Audit this contract →
← previous block·next block →recent activity