← previous blocknext block →recent activity
Analyzing
Block #104,868,148
23 transactions · 21 stateful · 2026-09-14 22:37:58 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,868,148 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w17w09w011w114w015w116w217w319w020w221w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x711ceb8d…5202
0x34b655…2a6f
8 touches
6 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0xfd2f61b3…a8bc
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x81d64349…50fe
0x34b655…2a6f
6 touches
3 conflicts
0x84611dd3…b345
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0x711ceb8da2…d35202
Audit this contract →
← previous block·next block →recent activity