← previous blocknext block →recent activity
Analyzing
Block #100,752,103
19 transactions · 19 stateful · 2026-08-31 12:08:48 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1.26
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,752,103 · 19 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
1w05w06w18w19w210w211w312w413w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x9482a067…eba9
0x34b655…2a6f
10 touches
10 conflicts
0xbaf55936…7584
0x851145…3f07
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
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: 0x01bff417…bc1071
10 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity