← previous blocknext block →recent activity
Analyzing
Block #105,845,547
35 transactions · 32 stateful · 2026-09-18 08:38:40 UTC
Parallelism
57/100
Blocked
59%
Avg conflicts / tx
2.17
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,845,547 · 35 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w09w210w312w421w623w724w825w926w1027w1128w1229w1330w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52dfe1ab…4172
0x34b655…2a6f
14 touches
21 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
10 touches
10 conflicts
0x7dafda9c…6c6a
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
21 conflicts on slot 0x52dfe1abc1…a54172
Audit this contract →
← previous block·next block →recent activity