← previous blocknext block →recent activity
Analyzing
Block #105,542,311
17 transactions · 14 stateful · 2026-09-17 07:10:57 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,542,311 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w010w011w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cc51e8f…2e71
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x86bd79a5…1f48
0x34b655…2a6f
4 touches
1 conflict
0x70f537e8…399b
0x34b655…2a6f
4 touches
1 conflict
0x4bdcb916…8da9
0x34b655…2a6f
4 touches
1 conflict
0xc2cd969d…db3b
0xd32edf…ff58
3 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
3 conflicts on slot 0x3cc51e8f05…3d2e71
Audit this contract →
← previous block·next block →recent activity