← previous blocknext block →recent activity
Analyzing
Block #100,419,541
12 transactions · 9 stateful · 2026-08-30 08:15:45 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,419,541 · 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a69c7c5…09cc
0x34b655…2a6f
4 touches
1 conflict
0xbeb54278…4eb5
0x34b655…2a6f
4 touches
1 conflict
0x7ef4ba09…2a25
0x34b655…2a6f
4 touches
1 conflict
0xd6601794…8a48
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x9fd29b24…b884
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
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 0x1a69c7c52c…7b09cc
Audit this contract →
← previous block·next block →recent activity