← previous blocknext block →recent activity
Analyzing
Block #104,194,538
20 transactions · 20 stateful · 2026-09-12 13:43:41 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
2.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,194,538 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w310w411w512w614w715w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0da71bf6…4d35
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb5924647…4cf1
0x34b655…2a6f
6 touches
3 conflicts
0x8bd00bf7…752d
0x34b655…2a6f
6 touches
3 conflicts
0x0728ec77…146c
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
21 conflicts on slot 0x0da71bf647…1b4d35
Audit this contract →
← previous block·next block →recent activity