← previous blocknext block →recent activity
Analyzing
Block #93,279,726
15 transactions · 14 stateful · 2026-08-05 06:50:08 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,279,726 · 15 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
2w03w06w17w08w19w210w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x0ea966…0742
8 touches
6 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
8 touches
6 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
8 touches
6 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x342222e8…2ec4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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: 0x0ea96615…ff0742
6 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity