← previous blocknext block →recent activity
Analyzing
Block #93,301,174
8 transactions · 7 stateful · 2026-08-05 08:37:58 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,301,174 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x58d6b9cf…7c9e
0x34b655…2a6f
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1e4a70cf…148a
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2b96d534…b6b5
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x3b3b15e2…af9f
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x0f2d78b1bb…5e7363
Audit this contract →
← previous block·next block →recent activity