← previous blocknext block →recent activity
Analyzing
Block #106,224,380
24 transactions · 24 stateful · 2026-09-19 16:26:20 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,224,380 · 24 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
5w08w09w010w111w214w115w117w018w120w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22187aaf…c0d5
0x34b655…2a6f
6 touches
3 conflicts
0x2f50c84a…3640
0x34b655…2a6f
6 touches
3 conflicts
0x3aca64ec…7cbb
0x34b655…2a6f
6 touches
3 conflicts
0x4fb437cc…05f7
0x34b655…2a6f
6 touches
3 conflicts
0x634015e1…0b09
0x34b655…2a6f
6 touches
3 conflicts
0x7499cc33…a306
0x34b655…2a6f
6 touches
3 conflicts
0x7eb3ae1e…a1a3
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity