← previous blocknext block →recent activity
Analyzing
Block #100,048,338
13 transactions · 12 stateful · 2026-08-29 01:03:42 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,048,338 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w210w311w412w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf494f6c9…714f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x413bd1e2…dfec
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xf494f6c99a…52714f
Audit this contract →
← previous block·next block →recent activity