← previous blocknext block →recent activity
Analyzing
Block #100,859,671
11 transactions · 9 stateful · 2026-08-31 21:10:20 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,859,671 · 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
1w06w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x0e30130b…ca64
0x6657d1…8ccc
2 touches
0 conflicts
0x1b338b3a…8e5c
0x6657d1…8ccc
2 touches
0 conflicts
0x335ed210…e60c
0x6657d1…8ccc
2 touches
0 conflicts
0x3f2b4c8f…9494
0x6657d1…8ccc
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity