← previous blocknext block →recent activity
Analyzing
Block #99,669,504
14 transactions · 13 stateful · 2026-08-27 17:10:10 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,669,504 · 14 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
5w08w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53eac009…b61b
0x34b655…2a6f
4 touches
1 conflict
0x1c840894…764a
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0b526ab3…3217
0x34b655…2a6f
2 touches
0 conflicts
0x14c20fe2…1c19
0x34b655…2a6f
2 touches
0 conflicts
0x37d2d6e6…356d
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 0x53eac00933…f3b61b
Audit this contract →
← previous block·next block →recent activity