← previous blocknext block →recent activity
Analyzing
Block #104,032,597
21 transactions · 18 stateful · 2026-09-12 00:00:06 UTC
Parallelism
62/100
Blocked
39%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,032,597 · 21 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
7w011w112w213w314w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78efe143…580b
0x34b655…2a6f
14 touches
21 conflicts
0xe66201d4…84f1
0x34b655…2a6f
14 touches
21 conflicts
0xd911522b…e960
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xd8ccb966…38e3
0x34b655…2a6f
12 touches
15 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
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
21 conflicts on slot 0x78efe14337…61580b
Audit this contract →
← previous block·next block →recent activity