← previous blocknext block →recent activity
Analyzing
Block #93,248,143
12 transactions · 12 stateful · 2026-08-05 04:11:20 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,248,143 · 12 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
2w04w05w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x0d4ff179…5538
0x34b655…2a6f
2 touches
0 conflicts
0x15a76f59…f29c
0x34b655…2a6f
2 touches
0 conflicts
0x37d710c8…45c1
0x34b655…2a6f
2 touches
0 conflicts
0x7754e0f5…d02e
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 0xf9e23360ff…e88ef7
Audit this contract →
← previous block·next block →recent activity