← previous blocknext block →recent activity
Analyzing
Block #93,658,214
10 transactions · 9 stateful · 2026-08-06 14:32:56 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,658,214 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb44
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb45
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6956d31b…6393
0x34b655…2a6f
4 touches
1 conflict
0x0a91ef44…f8f4
0x34b655…2a6f
2 touches
0 conflicts
0x0fa2a869…313e
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
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 0x231ccc1338…7fa7c6
Audit this contract →
← previous block·next block →recent activity