← previous blocknext block →recent activity
Analyzing
Block #100,738,914
24 transactions · 22 stateful · 2026-08-31 11:02:28 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,738,914 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w010w011w112w313w014w115w216w317w419w022w423w5
- 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
0x1bfd1f1d…724f
0x851145…3f07
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe61a3df2…f763
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x753b2da4…7a6d
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