← previous blocknext block →recent activity
Analyzing
Block #93,314,946
16 transactions · 13 stateful · 2026-08-05 09:47:12 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,314,946 · 16 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
2w03w16w27w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x496e3020…0c46
0x34b655…2a6f
2 touches
0 conflicts
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 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity