← previous blocknext block →recent activity
Analyzing
Block #93,200,399
19 transactions · 19 stateful · 2026-08-05 00:11:19 UTC
Parallelism
84/100
Blocked
21%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,200,399 · 19 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
1w02w03w17w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69ba9e8…e56a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0x3ee79352…037f
0x34b655…2a6f
4 touches
1 conflict
0x56fed0dd…581f
0x34b655…2a6f
4 touches
1 conflict
0x56fed0dd…5820
0x34b655…2a6f
4 touches
1 conflict
0x5a812049…d85d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xa69ba9e806…2de56a
Audit this contract →
← previous block·next block →recent activity