← previous blocknext block →recent activity
Analyzing
Block #93,137,668
21 transactions · 18 stateful · 2026-08-04 18:55:49 UTC
Parallelism
76/100
Blocked
22%
Avg conflicts / tx
0.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,137,668 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w213w318w020w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x560b6fd9…a104
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0xae28870c…072f
0x34b655…2a6f
4 touches
1 conflict
0xbe0e425c…9813
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x54ff4977…6281
0x34b655…2a6f
2 touches
0 conflicts
0x5e0bf019…75fd
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 0x560b6fd95c…4ca104
Audit this contract →
← previous block·next block →recent activity