← previous blocknext block →recent activity
Analyzing
Block #105,846,014
41 transactions · 39 stateful · 2026-09-18 08:41:00 UTC
Parallelism
63/100
Blocked
62%
Avg conflicts / tx
2.88
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,846,014 · 41 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
1w02w03w14w05w17w110w216w226w327w328w429w530w631w732w833w934w1035w1136w1237w1338w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0c27941…a6b9
0x34b655…2a6f
22 touches
55 conflicts
0x067c87f1…e98a
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0xb0c279414e…b9a6b9
Audit this contract →
← previous block·next block →recent activity