← previous blocknext block →recent activity
Analyzing
Block #93,390,033
18 transactions · 17 stateful · 2026-08-05 16:04:45 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,390,033 · 18 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
4w05w16w17w014w215w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x231ccc13…a7c6
0x34b655…2a6f
6 touches
3 conflicts
0x0a7a49dc…a295
0x34b655…2a6f
4 touches
1 conflict
0x123650c5…8859
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xf5c75a87…787c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x36e19f70…dffb
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 0x231ccc1338…7fa7c6
Audit this contract →
← previous block·next block →recent activity