← previous blocknext block →recent activity
Analyzing
Block #106,224,872
22 transactions · 20 stateful · 2026-09-19 16:28:48 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,224,872 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w19w210w311w412w513w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xada087b9…4aca
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x88fc2a68…3918
0x34b655…2a6f
16 touches
28 conflicts
0x4fb437cc…05f7
0x34b655…2a6f
14 touches
21 conflicts
0x7499cc33…a306
0x34b655…2a6f
14 touches
21 conflicts
0x7eb3ae1e…a1a3
0x34b655…2a6f
14 touches
21 conflicts
0x98dd86bb…1edb
0x34b655…2a6f
14 touches
21 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
14 touches
21 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
28 conflicts on slot 0xada087b994…444aca
Audit this contract →
← previous block·next block →recent activity