← previous blocknext block →recent activity
Analyzing
Block #93,362,925
23 transactions · 20 stateful · 2026-08-05 13:48:26 UTC
Parallelism
87/100
Blocked
25%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,362,925 · 23 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
1w02w15w010w011w012w114w217w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ec32eb4…697e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa558e115…fc88
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 0x6ec32eb4c5…ca697e
Audit this contract →
← previous block·next block →recent activity