← previous blocknext block →recent activity
Analyzing
Block #93,232,904
20 transactions · 17 stateful · 2026-08-05 02:54:43 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,232,904 · 20 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
1w02w07w19w215w316w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x231ccc13…a7c6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0aeef2b4…12cf
0x34b655…2a6f
4 touches
1 conflict
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0x36cfb788…a2b0
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x646278ac…2ebf
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
6 conflicts on slot 0x231ccc1338…7fa7c6
Audit this contract →
← previous block·next block →recent activity