← previous blocknext block →recent activity
Analyzing
Block #105,749,389
16 transactions · 15 stateful · 2026-09-18 00:33:16 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,749,389 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w16w28w39w411w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x309f43d0…fa22
0x34b655…2a6f
12 touches
15 conflicts
0xc5847c4d…a65c
0x34b655…2a6f
10 touches
10 conflicts
0xdb1e37cb…90c9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf70db1c6…b140
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x6ed3ab3c…cf22
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x309f43d086…ccfa22
Audit this contract →
← previous block·next block →recent activity