← previous blocknext block →recent activity
Analyzing
Block #93,309,659
16 transactions · 13 stateful · 2026-08-05 09:20:38 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,309,659 · 16 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
1w02w15w07w18w29w310w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc21d7c…e062
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x21cb35dd…1f66
0x34b655…2a6f
4 touches
1 conflict
0x2dec0e73…3189
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
3 conflicts on slot 0xdfc21d7c53…51e062
Audit this contract →
← previous block·next block →recent activity