← previous blocknext block →recent activity
Analyzing
Block #104,204,745
17 transactions · 15 stateful · 2026-09-12 14:35:36 UTC
Parallelism
59/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,204,745 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w211w312w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x0deb5804…40c6
0x34b655…2a6f
4 touches
1 conflict
0x100812e9…12b7
0x34b655…2a6f
4 touches
1 conflict
0x14f03197…2dba
0x34b655…2a6f
4 touches
1 conflict
0x21db5c5e…e6f9
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity