← previous blocknext block →recent activity
Analyzing
Block #100,749,135
22 transactions · 19 stateful · 2026-08-31 11:53:53 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,749,135 · 22 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
6w07w19w210w312w014w115w216w320w021w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd4ad6932…3b5f
0x851145…3f07
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0x0e3b59e9…d9d0
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity