← previous blocknext block →recent activity
Analyzing
Block #100,591,352
20 transactions · 20 stateful · 2026-08-30 22:40:11 UTC
Parallelism
90/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,591,352 · 20 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
7w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc8f9abd…ee31
0x34b655…2a6f
4 touches
1 conflict
0x9c6a9da2…c628
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0281e083…66b4
0x34b655…2a6f
2 touches
0 conflicts
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x0e9337e1…9956
0x34b655…2a6f
2 touches
0 conflicts
0x168f75b5…b2d1
0x34b655…2a6f
2 touches
0 conflicts
0x330587fd…4cd7
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 0xdc8f9abd07…32ee31
Audit this contract →
← previous block·next block →recent activity