← previous blocknext block →recent activity
Analyzing
Block #93,474,308
18 transactions · 15 stateful · 2026-08-05 23:08:25 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,474,308 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w27w38w413w514w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe9155399…bba2
0x34b655…2a6f
4 touches
1 conflict
0x2fd61111…5bbc
0x34b655…2a6f
4 touches
1 conflict
0x4c3f4858…52de
0x34b655…2a6f
4 touches
1 conflict
0x91e8d927…3a11
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
10 conflicts on slot 0x52b477bcb8…5d7ccf
Audit this contract →
← previous block·next block →recent activity