← previous blocknext block →recent activity
Analyzing
Block #104,160,078
30 transactions · 28 stateful · 2026-09-12 10:48:54 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,160,078 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w28w010w114w015w116w319w426w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fde4971…aac9
0x34b655…2a6f
8 touches
6 conflicts
0xc0ae39b0…be5f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x1408e7c7…f324
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
6 conflicts on slot 0x5fde497131…e8aac9
Audit this contract →
← previous block·next block →recent activity