← previous blocknext block →recent activity
Analyzing
Block #105,618,317
21 transactions · 20 stateful · 2026-09-17 13:33:32 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,618,317 · 21 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
1w03w04w15w26w07w18w112w215w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd57adb0…b579
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0xfc2493d3…6898
0x34b655…2a6f
6 touches
3 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x5c492c79…6b79
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x7061d006…074d
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
6 conflicts on slot 0xdd57adb0e5…01b579
Audit this contract →
← previous block·next block →recent activity