← previous blocknext block →recent activity
Analyzing
Block #105,748,787
12 transactions · 12 stateful · 2026-09-18 00:30:14 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,748,787 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213b816c…a5e0
0x34b655…2a6f
4 touches
1 conflict
0x335324b6…542f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x050c4b37…578b
0x6657d1…8ccc
2 touches
0 conflicts
0x0748d104…714d
0x6657d1…8ccc
2 touches
0 conflicts
0xb5c1d5f6…712d
0x754704…b603
2 touches
0 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
1 conflict on slot 0x213b816cc7…d4a5e0
Audit this contract →
← previous block·next block →recent activity