← previous blocknext block →recent activity
Analyzing
Block #104,869,110
19 transactions · 19 stateful · 2026-09-14 22:42:48 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,869,110 · 19 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
1w02w03w14w25w36w47w18w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
12 touches
15 conflicts
0x3b6e959d…158f
0x34b655…2a6f
10 touches
10 conflicts
0xf5d99264…de4e
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xdc6df759…5f14
0x34b655…2a6f
8 touches
6 conflicts
0xc12e55e5…1c07
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc6abdbd8…415a
0x34b655…2a6f
2 touches
0 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 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity