← previous blocknext block →recent activity
Analyzing
Block #100,625,692
27 transactions · 26 stateful · 2026-08-31 01:32:56 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,625,692 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w07w19w011w114w115w216w319w120w221w124w225w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xced52463…05c2
0x34b655…2a6f
6 touches
3 conflicts
0xd3dfba89…c93c
0x34b655…2a6f
6 touches
3 conflicts
0x00500a94…20d5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x1dedc384…ff57
0x851145…3f07
6 touches
3 conflicts
0x2ce5d13f…f8a9
0x851145…3f07
6 touches
3 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity