← previous blocknext block →recent activity
Analyzing
Block #106,032,825
26 transactions · 26 stateful · 2026-09-19 00:22:16 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,032,825 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w08w112w113w214w316w017w118w422w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce6bd347…2ad0
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x592469af…6437
0x34b655…2a6f
4 touches
1 conflict
0x662e354e…e306
0x34b655…2a6f
4 touches
1 conflict
0x73eff9e1…025c
0x34b655…2a6f
4 touches
1 conflict
0x7677a58c…819a
0x34b655…2a6f
4 touches
1 conflict
0x9bbba741…0526
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 0xce6bd34721…cf2ad0
Audit this contract →
← previous block·next block →recent activity