← previous blocknext block →recent activity
Analyzing
Block #93,248,620
8 transactions · 7 stateful · 2026-08-05 04:13:44 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,248,620 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae5cb3e3…b10f
0x34b655…2a6f
6 touches
3 conflicts
0x89bc0d41…ae1b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf28d07b9…4fb2
0x34b655…2a6f
4 touches
1 conflict
0x059bff94…6c87
0x34b655…2a6f
2 touches
0 conflicts
0x0e22f39d…b92b
0x34b655…2a6f
2 touches
0 conflicts
0x0e391a2e…d634
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 0xae5cb3e39b…73b10f
Audit this contract →
← previous block·next block →recent activity