← previous blocknext block →recent activity
Analyzing
Block #93,441,403
24 transactions · 22 stateful · 2026-08-05 20:23:00 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,441,403 · 24 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
3w04w05w16w08w111w014w115w117w219w120w221w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x5502e1cc…3910
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity