← previous blocknext block →recent activity
Analyzing
Block #100,577,270
28 transactions · 22 stateful · 2026-08-30 21:29:21 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,577,270 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w011w113w016w019w121w125w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x021cd478…a6d4
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x56e0948c…5a34
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x72b725f8…8766
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
6 conflicts on slot 0x021cd478ea…b9a6d4
Audit this contract →
← previous block·next block →recent activity