← previous blocknext block →recent activity
Analyzing
Block #104,868,077
15 transactions · 13 stateful · 2026-09-14 22:37:37 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
1.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,868,077 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w29w010w311w412w513w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
12 touches
15 conflicts
0xdda1b89f…6eb4
0x34b655…2a6f
8 touches
6 conflicts
0xaa920d62…4c46
0x34b655…2a6f
8 touches
6 conflicts
0xfe2577ac…677b
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x55f15e8f…f9a5
0x34b655…2a6f
6 touches
3 conflicts
0xa3bcf0be…e10e
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
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
15 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity