← previous blocknext block →recent activity
Analyzing
Block #93,672,936
14 transactions · 13 stateful · 2026-08-06 15:46:56 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,672,936 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w09w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf275b4ca…57b8
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x51232c8c…f30c
0xe52b14…7230
6 touches
3 conflicts
0x51232c8c…f30e
0xe52b14…7230
6 touches
3 conflicts
0xa6e37efb…afc0
0xe52b14…7230
6 touches
3 conflicts
0x51d2f89d…a46f
0xe52b14…7230
5 touches
3 conflicts
0x83c059ad…ac48
0x34b655…2a6f
4 touches
1 conflict
0xaa9c420e…8b45
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: 0xe52b1424…bb7230
3 conflicts on slot 0xf275b4ca84…5d57b8
Audit this contract →
← previous block·next block →recent activity