← previous blocknext block →recent activity
Analyzing
Block #100,584,582
26 transactions · 23 stateful · 2026-08-30 22:06:07 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,584,582 · 26 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
5w06w07w18w29w010w113w214w015w121w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4c703ab…f8cf
0x34b655…2a6f
6 touches
3 conflicts
0xe0f57943…818d
0x34b655…2a6f
4 touches
1 conflict
0xe7ad475a…0e41
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xd376181c…f040
0x34b655…2a6f
4 touches
1 conflict
0x354e383e…817c
0xa6afd3…d132
4 touches
1 conflict
0x2113891d…b0f7
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 0xb4c703ab76…fdf8cf
Audit this contract →
← previous block·next block →recent activity