← previous blocknext block →recent activity
Analyzing
Block #100,128,128
9 transactions · 8 stateful · 2026-08-29 07:45:25 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,128,128 · 9 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
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf98c943e…7c44
0x34b655…2a6f
4 touches
1 conflict
0x00570e68…046f
0x34b655…2a6f
2 touches
0 conflicts
0x01111065…feb0
0x34b655…2a6f
2 touches
0 conflicts
0x02a28d4f…c5d6
0x34b655…2a6f
2 touches
0 conflicts
0x02bfdbf9…6514
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 0x19795ad604…434a16
Audit this contract →
← previous block·next block →recent activity