← previous blocknext block →recent activity
Analyzing
Block #105,848,252
34 transactions · 32 stateful · 2026-09-18 08:52:16 UTC
Parallelism
59/100
Blocked
63%
Avg conflicts / tx
2.71
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,848,252 · 34 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w110w214w317w318w419w520w621w722w723w824w925w1026w1127w1230w732w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5c0d2f…7301
0x34b655…2a6f
16 touches
28 conflicts
0x8db32935…81a7
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xc10b903d…2f54
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
10 touches
10 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
10 touches
10 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 0x1a5c0d2fa1…937301
Audit this contract →
← previous block·next block →recent activity