← previous blocknext block →recent activity
Analyzing
Block #105,881,612
19 transactions · 18 stateful · 2026-09-18 11:40:10 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,881,612 · 19 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
1w02w16w07w18w19w210w311w412w513w614w717w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64b18423…c4d0
0x34b655…2a6f
14 touches
21 conflicts
0xb2560305…f27d
0x34b655…2a6f
10 touches
10 conflicts
0x64f182c6…e42d
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0xee8237bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0x297de2d5…7396
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
21 conflicts on slot 0x64b184239d…68c4d0
Audit this contract →
← previous block·next block →recent activity