← previous blocknext block →recent activity
Analyzing
Block #99,181,419
28 transactions · 24 stateful · 2026-08-26 00:06:05 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,181,419 · 28 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
4w05w17w08w19w211w013w014w115w019w120w221w223w024w126w027w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4c6da38…3a6a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x7598abcc…868f
0x34b655…2a6f
4 touches
1 conflict
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0x8ba18cc2…5afd
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
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 0xa4c6da388f…913a6a
Audit this contract →
← previous block·next block →recent activity