← previous blocknext block →recent activity
Analyzing
Block #104,033,159
18 transactions · 17 stateful · 2026-09-12 00:02:58 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,033,159 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w010w111w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3013c848…bd3c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0x45de70d9…e1dc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xe3a349af…4deb
0x34b655…2a6f
4 touches
1 conflict
0x8f153520…8dc4
0xa9da3c…540f
2 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0x3013c84851…07bd3c
Audit this contract →
← previous block·next block →recent activity