← previous blocknext block →recent activity
Analyzing
Block #104,024,118
15 transactions · 15 stateful · 2026-09-11 23:17:07 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,024,118 · 15 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
3w04w18w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9efe106e…72d2
0x34b655…2a6f
10 touches
10 conflicts
0x939cdd56…00c8
0x34b655…2a6f
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
6 touches
3 conflicts
0x10379e8d…3675
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x30908823…a62d
0x34b655…2a6f
4 touches
1 conflict
0x39126904…24d8
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
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
10 conflicts on slot 0x9efe106ebb…ad72d2
Audit this contract →
← previous block·next block →recent activity