← previous blocknext block →recent activity
Analyzing
Block #99,093,231
18 transactions · 16 stateful · 2026-08-25 16:42:19 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,093,231 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w112w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9c05bd7…8cc8
0x34b655…2a6f
4 touches
1 conflict
0xf79f04fe…a715
0x34b655…2a6f
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x79d833b4…d22c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe0ce1be3…0b45
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
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 0xd9c05bd756…388cc8
Audit this contract →
← previous block·next block →recent activity