← previous blocknext block →recent activity
Analyzing
Block #105,749,719
33 transactions · 31 stateful · 2026-09-18 00:34:56 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,749,719 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w19w210w320w323w325w426w527w628w729w830w931w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5847c4d…a65c
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6ed3ab3c…cf22
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0x4ab195e7…0967
0x34b655…2a6f
8 touches
6 conflicts
0x5108e265…f5b8
0x34b655…2a6f
8 touches
6 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 0xc5847c4d32…49a65c
Audit this contract →
← previous block·next block →recent activity