← previous blocknext block →recent activity
Analyzing
Block #104,869,125
17 transactions · 17 stateful · 2026-09-14 22:42:53 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
1.12
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,869,125 · 17 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
1w02w15w08w09w110w212w213w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
10 touches
10 conflicts
0xc12e55e5…1c07
0x34b655…2a6f
8 touches
6 conflicts
0xf38a3927…ad62
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x60ce2df9…5a39
0x34b655…2a6f
6 touches
3 conflicts
0x9f2bf688…a44f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
10 conflicts on slot 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity