← previous blocknext block →recent activity
Analyzing
Block #104,024,618
15 transactions · 15 stateful · 2026-09-11 23:19:40 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,024,618 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w09w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1321758b…6798
0x34b655…2a6f
8 touches
6 conflicts
0x2e0edc98…9765
0x34b655…2a6f
4 touches
1 conflict
0x30908823…a62d
0x34b655…2a6f
4 touches
1 conflict
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd1448207…452d
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0xfc8cd993…5c11
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
6 conflicts on slot 0x1321758ba2…df6798
Audit this contract →
← previous block·next block →recent activity