← previous blocknext block →recent activity
Analyzing
Block #104,847,744
18 transactions · 18 stateful · 2026-09-14 20:55:13 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,847,744 · 18 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
1w02w13w24w35w48w09w110w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd06cc746…27e4
0x93a451…d286
10 touches
10 conflicts
0xeb6860e2…3ca4
0x93a451…d286
10 touches
10 conflicts
0x38aa1898…fdf5
0x3bd359…433a
10 touches
10 conflicts
0xebf7d7fd…0a9a
0x188d58…ea8e
10 touches
10 conflicts
0xebf7d7fd…0a99
0x188d58…ea8e
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x25d89b13…0f3e
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: 0x93a4519b…d1d286
10 conflicts on slot 0xd06cc7460d…e927e4
Audit this contract →
← previous block·next block →recent activity