← previous blocknext block →recent activity
Analyzing
Block #100,635,662
12 transactions · 12 stateful · 2026-08-31 02:23:05 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,635,662 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaa5e459…c7eb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x03cabc68…bc3b
0x34b655…2a6f
2 touches
0 conflicts
0x29354600…7b17
0x34b655…2a6f
2 touches
0 conflicts
0x3861b165…8482
0x34b655…2a6f
2 touches
0 conflicts
0x6d5c5d72…914b
0x34b655…2a6f
2 touches
0 conflicts
0x788c94ad…d632
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
1 conflict on slot 0xcaa5e45985…ccc7eb
Audit this contract →
← previous block·next block →recent activity