← previous blocknext block →recent activity
Analyzing
Block #104,192,867
14 transactions · 13 stateful · 2026-09-12 13:35:07 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,192,867 · 14 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
2w04w17w08w19w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xf8cb14ea…b0eb
0x34b655…2a6f
6 touches
3 conflicts
0x8ac39e10…2cf8
0x34b655…2a6f
6 touches
3 conflicts
0xa527a5f0…89ca
0x34b655…2a6f
4 touches
1 conflict
0xabb9f292…17a3
0x34b655…2a6f
4 touches
1 conflict
0xb9f0b0dc…4827
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 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity