← previous blocknext block →recent activity
Analyzing
Block #100,034,249
27 transactions · 24 stateful · 2026-08-28 23:52:47 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,034,249 · 27 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w012w120w021w124w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f52eeeb…12b9
0x34b655…2a6f
6 touches
3 conflicts
0x274ee839…ec80
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0xa6b48d6e…0705
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
3 conflicts on slot 0x9f52eeebff…b612b9
Audit this contract →
← previous block·next block →recent activity