← previous blocknext block →recent activity
Analyzing
Block #93,503,090
13 transactions · 11 stateful · 2026-08-06 01:33:07 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,503,090 · 13 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda7f5f6e…89cd
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0ab1986a…4790
0x34b655…2a6f
2 touches
0 conflicts
0x0e3b59e9…d9d0
0x34b655…2a6f
2 touches
0 conflicts
0x14ea9ada…e627
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
1 conflict on slot 0xda7f5f6e8c…5789cd
Audit this contract →
← previous block·next block →recent activity