← previous blocknext block →recent activity
Analyzing
Block #93,244,898
9 transactions · 7 stateful · 2026-08-05 03:55:00 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,244,898 · 9 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
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0xe5ef6ee0…dfa0
0x34b655…2a6f
4 touches
1 conflict
0xd4eb728f…0d4e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0x8f52773e…f46a
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 0x7d0eaae22e…4260b7
Audit this contract →
← previous block·next block →recent activity