← previous blocknext block →recent activity
Analyzing
Block #100,739,610
21 transactions · 21 stateful · 2026-08-31 11:05:58 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,739,610 · 21 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
3w08w09w110w211w212w013w114w215w316w419w520w1
- 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
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x9deccfa6…22bf
0x851145…3f07
7 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x508f0ac7…59be
0x851145…3f07
5 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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