← previous blocknext block →recent activity
Analyzing
Block #93,474,723
26 transactions · 24 stateful · 2026-08-05 23:10:31 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,474,723 · 26 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
1w02w17w08w19w215w316w417w219w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb469535a…e19e
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc6b9bb4b…145a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afa9
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afaa
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
10 conflicts on slot 0xb469535a5a…b6e19e
Audit this contract →
← previous block·next block →recent activity