← previous blocknext block →recent activity
Analyzing
Block #104,870,272
17 transactions · 16 stateful · 2026-09-14 22:48:39 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,870,272 · 17 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
3w04w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
10 touches
10 conflicts
0x7504da64…542f
0x34b655…2a6f
10 touches
10 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
6 touches
3 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xbc0b43b0…35d6
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x43eeb6cb…aca3
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
10 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity