← previous blocknext block →recent activity
Analyzing
Block #93,551,029
18 transactions · 17 stateful · 2026-08-06 05:34:06 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
1.06
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,551,029 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w18w29w010w111w212w314w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xe96cbc90…be66
0x754704…b603
6 touches
3 conflicts
0xeb0b1d43…9559
0x34b655…2a6f
6 touches
3 conflicts
0x2c3dbd78…1a68
0x34b655…2a6f
6 touches
3 conflicts
0x803eb45d…00bd
0x34b655…2a6f
4 touches
1 conflict
0x99c5409a…25b7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity