← previous blocknext block →recent activity
Analyzing
Block #93,314,865
14 transactions · 12 stateful · 2026-08-05 09:46:48 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,314,865 · 14 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
7w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ae3e2cf…d1a9
0x34b655…2a6f
4 touches
1 conflict
0x3e72a2d1…ce0e
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0xba3b3ce2…6dc6
0x1c8a33…d316
2 touches
0 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
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 0x8ae3e2cf9e…59d1a9
Audit this contract →
← previous block·next block →recent activity