← previous blocknext block →recent activity
Analyzing
Block #104,192,812
20 transactions · 17 stateful · 2026-09-12 13:34:50 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,192,812 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w111w212w314w415w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45de70d9…e1dc
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x20282983…15f3
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x77498c8d…5665
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xfa324e43…889a
0x1b6862…e19c
6 touches
3 conflicts
0x51fc8795…126f
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
21 conflicts on slot 0x45de70d9be…64e1dc
Audit this contract →
← previous block·next block →recent activity