← previous blocknext block →recent activity
Analyzing
Block #104,194,467
21 transactions · 19 stateful · 2026-09-12 13:43:20 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,194,467 · 21 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
1w04w08w19w212w013w114w215w318w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0b39b82…c11e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed530c…d450
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
10 conflicts on slot 0xb0b39b820f…cbc11e
Audit this contract →
← previous block·next block →recent activity