← previous blocknext block →recent activity
Analyzing
Block #105,608,713
24 transactions · 21 stateful · 2026-09-17 12:45:11 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,608,713 · 24 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
1w02w05w16w18w09w110w111w112w213w215w321w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ecbbe7…f713
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3347cbe5…846c
0x34b655…2a6f
6 touches
3 conflicts
0x48de9cd5…2f4c
0x34b655…2a6f
6 touches
3 conflicts
0x545e527e…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0x62d6e82b…a750
0x34b655…2a6f
6 touches
3 conflicts
0x75ac5fa0…1808
0x34b655…2a6f
6 touches
3 conflicts
0x7f127ad0…2bd6
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xa7ecbbe767…04f713
Audit this contract →
← previous block·next block →recent activity