← previous blocknext block →recent activity
Analyzing
Block #100,630,830
11 transactions · 11 stateful · 2026-08-31 01:58:47 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,630,830 · 11 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x87164342…7715
0x34b655…2a6f
4 touches
1 conflict
0x9eaed5a0…9f17
0x34b655…2a6f
4 touches
1 conflict
0x5a95f394…be66
0x34b655…2a6f
4 touches
1 conflict
0x517ce34a…f09a
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x6bab0076…422b
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
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 0x4a5956ef63…f0e226
Audit this contract →
← previous block·next block →recent activity