← previous blocknext block →recent activity
Analyzing
Block #104,023,733
15 transactions · 14 stateful · 2026-09-11 23:15:10 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,023,733 · 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
2w03w14w27w08w39w411w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb575cf74…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf407a637…7cc0
0x34b655…2a6f
4 touches
1 conflict
0x608b58e0…11b7
0x34b655…2a6f
4 touches
1 conflict
0x15ee0da2…4dcf
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 0xb575cf748f…befbd5
Audit this contract →
← previous block·next block →recent activity