← previous blocknext block →recent activity
Analyzing
Block #104,333,527
35 transactions · 33 stateful · 2026-09-13 01:28:54 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,333,527 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w413w520w621w722w132w233w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d32fccb…7cce
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
8 touches
6 conflicts
0x62910921…3016
0x34b655…2a6f
8 touches
6 conflicts
0xfc2493d3…6898
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x8d32fccb19…607cce
Audit this contract →
← previous block·next block →recent activity