← previous blocknext block →recent activity
Analyzing
Block #104,878,051
22 transactions · 22 stateful · 2026-09-14 23:27:48 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,878,051 · 22 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
2w03w16w28w39w410w511w315w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
16 touches
28 conflicts
0x39f96589…5188
0x34b655…2a6f
10 touches
10 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0x9f4801c8…0afe
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x10bb734d…dacf
0x34b655…2a6f
6 touches
3 conflicts
0xdb9b1828…590b
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
28 conflicts on slot 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity