← previous blocknext block →recent activity
Analyzing
Block #104,166,326
12 transactions · 10 stateful · 2026-09-12 11:20:37 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,166,326 · 12 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
2w05w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9be3f18…bc0d
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe7b9eede…2538
0x34b655…2a6f
4 touches
1 conflict
0xf42e9f99…5f09
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
2 touches
0 conflicts
0x82aec64d…a6a3
0x34b655…2a6f
2 touches
0 conflicts
0x861a5d3d…e5f4
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 0xa9be3f1876…cdbc0d
Audit this contract →
← previous block·next block →recent activity