← previous blocknext block →recent activity
Analyzing
Block #104,024,435
16 transactions · 14 stateful · 2026-09-11 23:18:44 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,024,435 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w39w312w413w515w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd35dad2b…1922
0x34b655…2a6f
12 touches
15 conflicts
0x30908823…a62d
0x34b655…2a6f
10 touches
10 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0x1bb56de3…732e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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
15 conflicts on slot 0xd35dad2ba3…1e1922
Audit this contract →
← previous block·next block →recent activity