← previous blocknext block →recent activity
Analyzing
Block #93,456,977
11 transactions · 11 stateful · 2026-08-05 21:41:18 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,456,977 · 11 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc601b84f…92e7
0x34b655…2a6f
4 touches
1 conflict
0x82e925dc…9938
0x34b655…2a6f
4 touches
1 conflict
0xe0e00683…e335
0x34b655…2a6f
4 touches
1 conflict
0x9a8af3c2…e4ae
0x34b655…2a6f
4 touches
1 conflict
0x84e3ed5a…1678
0x34b655…2a6f
2 touches
0 conflicts
0x84e3ed5a…1679
0x34b655…2a6f
2 touches
0 conflicts
0xd178eda9…f308
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0xc601b84fe3…3592e7
Audit this contract →
← previous block·next block →recent activity