← previous blocknext block →recent activity
Analyzing
Block #104,195,040
18 transactions · 17 stateful · 2026-09-12 13:46:14 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
1.94
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,195,040 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w511w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28ea43af…a9c1
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x63f544f5…174f
0x34b655…2a6f
6 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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
28 conflicts on slot 0x28ea43af82…baa9c1
Audit this contract →
← previous block·next block →recent activity