← previous blocknext block →recent activity
Analyzing
Block #104,333,591
26 transactions · 20 stateful · 2026-09-13 01:29:13 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,333,591 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w112w213w314w419w020w122w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45de70d9…e1dc
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x3013c848…bd3c
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc38f208c…1dea
0x34b655…2a6f
6 touches
3 conflicts
0x2531b293…51c6
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x2bb0d58d…9dcf
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 0x45de70d9be…64e1dc
Audit this contract →
← previous block·next block →recent activity