← previous blocknext block →recent activity
Analyzing
Block #100,919,722
30 transactions · 28 stateful · 2026-09-01 02:12:23 UTC
Parallelism
80/100
Blocked
61%
Avg conflicts / tx
1.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,919,722 · 30 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
1w02w03w05w17w18w29w310w011w113w116w217w318w426w328w529w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe4978fe2…7b9b
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
8 touches
6 conflicts
0x22796a51…85b6
0x065c9d…c394
7 touches
6 conflicts
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity