← previous blocknext block →recent activity
Analyzing
Block #104,149,036
13 transactions · 12 stateful · 2026-09-12 09:52:45 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,149,036 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d8c0e3e…2aad
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0da41d10…d748
0x34b655…2a6f
2 touches
0 conflicts
0x0e8c1121…9885
0x34b655…2a6f
2 touches
0 conflicts
0x14f03197…2dba
0x34b655…2a6f
2 touches
0 conflicts
0x23de777d…0e95
0x34b655…2a6f
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
1 conflict on slot 0x3d8c0e3ee9…5e2aad
Audit this contract →
← previous block·next block →recent activity