← previous blocknext block →recent activity
Analyzing
Block #93,486,040
18 transactions · 17 stateful · 2026-08-06 00:07:24 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,486,040 · 18 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
2w03w17w09w010w112w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b9bb4b…145a
0x34b655…2a6f
6 touches
3 conflicts
0xb968c832…9b6a
0x99c7a7…8bf0
4 touches
1 conflict
0x0d528651…72f0
0x754704…b603
4 touches
1 conflict
0x40226d20…1ff7
0x754704…b603
4 touches
1 conflict
0xe96cbc90…be66
0x754704…b603
4 touches
1 conflict
0x51dd81b2…a171
0x99c7a7…8bf0
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x50c0dd87…1128
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 0xc6b9bb4b8d…cc145a
Audit this contract →
← previous block·next block →recent activity