← previous blocknext block →recent activity
Analyzing
Block #106,027,821
23 transactions · 19 stateful · 2026-09-18 23:57:05 UTC
Parallelism
83/100
Blocked
58%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,027,821 · 23 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
2w03w14w07w18w210w011w112w213w314w215w016w117w218w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1abd5c35…67c5
0x34b655…2a6f
8 touches
6 conflicts
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0x00fa0324…5771
0x34b655…2a6f
8 touches
6 conflicts
0x7ed54c43…9ced
0xd32edf…ff58
7 touches
6 conflicts
0x45885570…ed97
0x34b655…2a6f
6 touches
3 conflicts
0x5371eb8f…845b
0x34b655…2a6f
6 touches
3 conflicts
0x68292fe7…d918
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0x1abd5c3571…0167c5
Audit this contract →
← previous block·next block →recent activity