← previous blocknext block →recent activity
Analyzing
Block #93,289,059
23 transactions · 21 stateful · 2026-08-05 07:37:04 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,289,059 · 23 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
4w05w16w27w38w414w315w316w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30d0d690…a28f
0x34b655…2a6f
8 touches
6 conflicts
0xff68510a…09f1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdf6c3e51…c493
0x34b655…2a6f
4 touches
1 conflict
0xfe768012…b65e
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
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 0x30d0d6909c…72a28f
Audit this contract →
← previous block·next block →recent activity