← previous blocknext block →recent activity
Analyzing
Block #104,325,834
19 transactions · 17 stateful · 2026-09-13 00:49:51 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,325,834 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w011w112w213w014w115w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b8fbde…396d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x818e1296…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x8deb02b3…0280
0x34b655…2a6f
4 touches
1 conflict
0xf72228f6…970c
0x34b655…2a6f
4 touches
1 conflict
0x14ee2daf…a775
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
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
6 conflicts on slot 0xa8b8fbdeaa…29396d
Audit this contract →
← previous block·next block →recent activity