← previous blocknext block →recent activity
Analyzing
Block #93,075,790
19 transactions · 17 stateful · 2026-08-04 13:43:56 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,075,790 · 19 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
1w02w13w04w17w28w39w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758a0dd5…0f46
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf796eaef…fac5
0x34b655…2a6f
4 touches
1 conflict
0xf7bcb61d…e96f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
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
1 conflict on slot 0x758a0dd50c…2a0f46
Audit this contract →
← previous block·next block →recent activity