← previous blocknext block →recent activity
Analyzing
Block #104,160,742
17 transactions · 16 stateful · 2026-09-12 10:52:15 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,160,742 · 17 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
4w010w011w114w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf30cdba3…6083
0x34b655…2a6f
4 touches
1 conflict
0x25495774…d0db
0x34b655…2a6f
2 touches
0 conflicts
0x3053e7b9…9298
0x34b655…2a6f
2 touches
0 conflicts
0x349e04a3…7a52
0x34b655…2a6f
2 touches
0 conflicts
0x3db9ec81…a6f8
0x34b655…2a6f
2 touches
0 conflicts
0x420a4645…95fe
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity