← previous blocknext block →recent activity
Analyzing
Block #105,852,271
26 transactions · 25 stateful · 2026-09-18 09:12:30 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,852,271 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w011w112w213w317w018w219w320w421w523w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56a78e60…72fb
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
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 0x56a78e60a6…3f72fb
Audit this contract →
← previous block·next block →recent activity