← previous blocknext block →recent activity
Analyzing
Block #100,124,197
27 transactions · 24 stateful · 2026-08-29 07:25:38 UTC
Parallelism
70/100
Blocked
54%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,124,197 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w07w19w010w111w112w215w216w317w421w122w424w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x627738d1…db02
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x6aa2827e…9709
0x34b655…2a6f
6 touches
3 conflicts
0x067407e2…3741
0xd32edf…ff58
5 touches
3 conflicts
0x9cf9008a…d826
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity