← previous blocknext block →recent activity
Analyzing
Block #105,539,077
18 transactions · 18 stateful · 2026-09-17 06:54:40 UTC
Parallelism
56/100
Blocked
39%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,539,077 · 18 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
7w08w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd63fb8e3…6117
0x34b655…2a6f
8 touches
6 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
8 touches
6 conflicts
0x8c6fb845…5b67
0x34b655…2a6f
8 touches
6 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
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
6 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity