← previous blocknext block →recent activity
Analyzing
Block #104,023,513
18 transactions · 18 stateful · 2026-09-11 23:14:03 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,023,513 · 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
1w03w010w113w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e0edc98…9765
0x34b655…2a6f
6 touches
3 conflicts
0xd1448207…452d
0x34b655…2a6f
4 touches
1 conflict
0x2592d715…a50e
0x34b655…2a6f
4 touches
1 conflict
0x2810c74b…0e91
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x61ca6437…2142
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x8eb21bd9…aa8b
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
3 conflicts on slot 0x2e0edc98a5…b09765
Audit this contract →
← previous block·next block →recent activity