← previous blocknext block →recent activity
Analyzing
Block #100,979,620
21 transactions · 18 stateful · 2026-09-01 07:13:41 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,979,620 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w19w111w012w116w019w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191e0467…70e5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x71ab2d1a…af06
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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: Perpl
3 conflicts on slot 0x191e0467ba…1470e5
Audit this contract →
← previous block·next block →recent activity