← previous blocknext block →recent activity
Analyzing
Block #99,618,840
13 transactions · 11 stateful · 2026-08-27 12:54:19 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,618,840 · 13 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
3w04w18w09w110w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23c1dd54…8fdf
0x34b655…2a6f
4 touches
1 conflict
0xea154cbb…f280
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xf8f8019d…10cf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x27e82965…890f
0x34b655…2a6f
2 touches
0 conflicts
0x3e49348b…9445
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 0x23c1dd540a…688fdf
Audit this contract →
← previous block·next block →recent activity