← previous blocknext block →recent activity
Analyzing
Block #93,345,862
19 transactions · 17 stateful · 2026-08-05 12:22:38 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,345,862 · 19 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
5w06w18w09w112w216w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x808129fc…f97d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x295faadc…ed75
0x34b655…2a6f
4 touches
1 conflict
0xc4dc32ca…83f9
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 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity