← previous blocknext block →recent activity
Analyzing
Block #104,868,816
15 transactions · 13 stateful · 2026-09-14 22:41:20 UTC
Parallelism
53/100
Blocked
69%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,868,816 · 15 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
2w03w14w15w26w37w410w511w612w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x0987681e…1acf
0x34b655…2a6f
8 touches
6 conflicts
0x8589dbca…d057
0x34b655…2a6f
6 touches
3 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0x736fafee…8bfc
0x34b655…2a6f
6 touches
3 conflicts
0xeb91761f…427f
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
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
21 conflicts on slot 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity