← previous blocknext block →recent activity
Analyzing
Block #104,877,506
25 transactions · 24 stateful · 2026-09-14 23:25:03 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,877,506 · 25 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
1w02w13w25w06w010w011w112w213w314w115w216w319w020w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbd35b2d…47bf
0x34b655…2a6f
8 touches
6 conflicts
0x1b6712ab…2da8
0x34b655…2a6f
8 touches
6 conflicts
0x26b2ba12…6ab9
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x79347b24…9fba
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x81716ce9…095f
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
6 conflicts on slot 0xfbd35b2df4…6847bf
Audit this contract →
← previous block·next block →recent activity