← previous blocknext block →recent activity
Analyzing
Block #92,407,629
14 transactions · 12 stateful · 2026-08-02 05:40:59 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,407,629 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe64d2555…8caf
0x34b655…2a6f
6 touches
3 conflicts
0x85971f5d…e920
0x34b655…2a6f
4 touches
1 conflict
0xc0fd7ba0…e1be
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x01a08f7d…dec6
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
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
3 conflicts on slot 0xe64d255503…c58caf
Audit this contract →
← previous block·next block →recent activity