← previous blocknext block →recent activity
Analyzing
Block #100,739,449
20 transactions · 14 stateful · 2026-08-31 11:05:10 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,739,449 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w39w210w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda3b445…e5c1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x54c8c0a4…812a
0x34b655…2a6f
6 touches
3 conflicts
0x4e135144…4167
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
4 touches
1 conflict
0xbf7817bc…52f6
0x34b655…2a6f
4 touches
1 conflict
0xcb21158b…f18d
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xfda3b4456b…f8e5c1
Audit this contract →
← previous block·next block →recent activity