← previous blocknext block →recent activity
Analyzing
Block #100,561,419
12 transactions · 9 stateful · 2026-08-30 20:09:36 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,561,419 · 12 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
5w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0xee96e028…d315
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x60269444…e8de
0x34b655…2a6f
2 touches
0 conflicts
0x6324ccc9…14fd
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity