← previous blocknext block →recent activity
Analyzing
Block #92,769,449
17 transactions · 15 stateful · 2026-08-03 12:01:58 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,769,449 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w07w18w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe6f98dc…7446
0x34b655…2a6f
4 touches
1 conflict
0x0d528651…72f0
0x754704…b603
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0xe96cbc90…be66
0x754704…b603
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
1 conflict on slot 0xfe6f98dc3a…bf7446
Audit this contract →
← previous block·next block →recent activity