← previous blocknext block →recent activity
Analyzing
Block #93,499,722
16 transactions · 15 stateful · 2026-08-06 01:16:11 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,499,722 · 16 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
3w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1b96e149…c982
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x4d971bc9…fadc
0x34b655…2a6f
2 touches
0 conflicts
0x4d971bc9…fadd
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 0x9fd37234c4…602731
Audit this contract →
← previous block·next block →recent activity