← previous blocknext block →recent activity
Analyzing
Block #106,300,851
17 transactions · 14 stateful · 2026-09-19 22:51:13 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,300,851 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w011w013w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67a9f76d…0b84
0x34b655…2a6f
4 touches
1 conflict
0xd1603130…9680
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd41f5136…97c6
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b85
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb2a6eba0…0499
0x065c9d…c394
3 touches
1 conflict
0x32070dd0…692b
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 0x67a9f76d91…400b84
Audit this contract →
← previous block·next block →recent activity