← previous blocknext block →recent activity
Analyzing
Block #93,064,310
16 transactions · 16 stateful · 2026-08-04 12:45:44 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,064,310 · 16 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
1w02w14w05w08w19w110w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x0600e909…c4f2
0x34b655…2a6f
4 touches
1 conflict
0x2e960d17…eb4c
0x34b655…2a6f
4 touches
1 conflict
0x606f046f…4453
0x34b655…2a6f
4 touches
1 conflict
0x6507044e…bcd6
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x7182a94f…dc78
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
1 conflict on slot 0xf324b40549…56ca30
Audit this contract →
← previous block·next block →recent activity