← previous blocknext block →recent activity
Analyzing
Block #99,444,214
12 transactions · 11 stateful · 2026-08-26 22:08:51 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,444,214 · 12 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
4w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x55010ec8…ea31
0x34b655…2a6f
2 touches
0 conflicts
0x5ae11a9d…16e0
0x34b655…2a6f
2 touches
0 conflicts
0x65bdc5fa…d7f3
0x34b655…2a6f
2 touches
0 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
2 touches
0 conflicts
0x7b67f6cf…0aab
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 0x5b6af0070f…160f35
Audit this contract →
← previous block·next block →recent activity