← previous blocknext block →recent activity
Analyzing
Block #100,739,192
22 transactions · 20 stateful · 2026-08-31 11:03:52 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,739,192 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w09w110w214w017w118w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd7443f37…eb79
0x34b655…2a6f
4 touches
1 conflict
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0xe98be4ff…d0a2
0x34b655…2a6f
4 touches
1 conflict
0xf16c46ce…fead
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity