← previous blocknext block →recent activity
Analyzing
Block #100,809,904
22 transactions · 22 stateful · 2026-08-31 16:59:47 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,809,904 · 22 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
1w02w03w15w07w09w110w214w215w316w420w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xdd3aa9b7…9ebe
0xd32edf…ff58
5 touches
3 conflicts
0xe49850c1…d209
0x851145…3f07
5 touches
3 conflicts
0xf8480e2a…dff1
0x1b6862…e19c
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
3 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity