← previous blocknext block →recent activity
Analyzing
Block #93,440,823
18 transactions · 17 stateful · 2026-08-05 20:20:05 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,440,823 · 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
2w03w14w26w08w09w110w011w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x3eba9517…1337
0x968279…9342
4 touches
1 conflict
0x3eba9517…1338
0x968279…9342
4 touches
1 conflict
0xea5e96ce…9948
0x968279…9342
4 touches
1 conflict
0xea5e96ce…9949
0x968279…9342
4 touches
1 conflict
0xea5e96ce…994b
0x968279…9342
4 touches
1 conflict
0x6d1b72ee…6b78
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity