← previous blocknext block →recent activity
Analyzing
Block #104,847,839
28 transactions · 24 stateful · 2026-09-14 20:55:42 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,847,839 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w08w116w017w118w219w021w322w124w226w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c168b41…7486
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0xf553d91c…8185
0x34b655…2a6f
6 touches
3 conflicts
0x092e2a78…173f
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x4265984a…a7d2
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
6 conflicts on slot 0x9c168b41b3…567486
Audit this contract →
← previous block·next block →recent activity