← previous blocknext block →recent activity
Analyzing
Block #93,350,354
10 transactions · 8 stateful · 2026-08-05 12:45:13 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,350,354 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x66f7c9fa…39a3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x03da5c00…b353
0x34b655…2a6f
2 touches
0 conflicts
0x898b360d…3513
0xea1b8e…c5ec
2 touches
0 conflicts
0x8e6c39f9…a26d
0xea1b8e…c5ec
2 touches
0 conflicts
0xa8abcc19…3d83
0xea1b8e…c5ec
2 touches
0 conflicts
0xaa2f6971…c549
0xea1b8e…c5ec
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 0x4f3a6b4a49…e93819
Audit this contract →
← previous block·next block →recent activity