← previous blocknext block →recent activity
Analyzing
Block #93,490,759
16 transactions · 14 stateful · 2026-08-06 00:31:07 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,490,759 · 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
2w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…598f
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…5990
0x34b655…2a6f
2 touches
0 conflicts
0x5110a94f…86d1
0x34b655…2a6f
2 touches
0 conflicts
0x5110a94f…86d2
0x34b655…2a6f
2 touches
0 conflicts
0x5f447bf3…57c7
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 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity