← previous blocknext block →recent activity
Analyzing
Block #93,399,236
28 transactions · 25 stateful · 2026-08-05 16:51:01 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,399,236 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w09w115w216w117w218w219w122w323w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x44e8f9f4…a5ad
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity