← previous blocknext block →recent activity
Analyzing
Block #104,205,726
19 transactions · 17 stateful · 2026-09-12 14:40:40 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,205,726 · 19 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
1w03w05w07w19w210w313w114w215w316w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5c8a8db2…8a6d
0x34b655…2a6f
6 touches
3 conflicts
0xddc5beb2…3f56
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x100812e9…12b7
0x34b655…2a6f
4 touches
1 conflict
0x3cf9ec3e…b3b8
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity