← previous blocknext block →recent activity
Analyzing
Block #93,663,574
12 transactions · 11 stateful · 2026-08-06 14:59:52 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,663,574 · 12 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
3w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9bd1e2be…740d
0x34b655…2a6f
4 touches
1 conflict
0x2adc238a…b92b
0x34b655…2a6f
2 touches
0 conflicts
0x2e22a171…b806
0x34b655…2a6f
2 touches
0 conflicts
0x3a874ce6…22d1
0x34b655…2a6f
2 touches
0 conflicts
0x65ca7c8d…6df7
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
3 conflicts on slot 0x1bf8d2afa1…d2d140
Audit this contract →
← previous block·next block →recent activity