← previous blocknext block →recent activity
Analyzing
Block #104,321,488
19 transactions · 18 stateful · 2026-09-13 00:27:47 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,321,488 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w010w212w313w414w515w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x40c6eb19…32bb
0x34b655…2a6f
8 touches
6 conflicts
0xe66201d4…84f1
0x34b655…2a6f
4 touches
1 conflict
0x5f55407c…ce96
0x065c9d…c394
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x74e1ffd8…9192
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity