← previous blocknext block →recent activity
Analyzing
Block #93,505,893
16 transactions · 16 stateful · 2026-08-06 01:47:13 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,505,893 · 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
2w03w17w28w310w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0x04e17b28…d9f0
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x3230413b…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x34cdb3c2…96d2
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x5b0687c2…037e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x94bb14fe40…668f47
Audit this contract →
← previous block·next block →recent activity