← previous blocknext block →recent activity
Analyzing
Block #104,333,333
15 transactions · 15 stateful · 2026-09-13 01:27:54 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,333,333 · 15 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
2w03w14w210w212w013w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6df1d50f…8a92
0x34b655…2a6f
4 touches
1 conflict
0xc0b7dd82…caa1
0x34b655…2a6f
3 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
0x573e497e…dab5
0x34b655…2a6f
2 touches
0 conflicts
0x5ac2c115…065a
0x34b655…2a6f
2 touches
0 conflicts
0x7cbbf8d5…4b14
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity