← previous blocknext block →recent activity
Analyzing
Block #93,926,286
16 transactions · 14 stateful · 2026-08-07 13:01:04 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,926,286 · 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
1w02w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3f6f7c8…2436
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2cffc55c…f961
0x34b655…2a6f
4 touches
1 conflict
0x10a0e8ee…ac08
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x23a89258…d863
0x34b655…2a6f
2 touches
0 conflicts
0x41377979…0a18
0x34b655…2a6f
2 touches
0 conflicts
0x4cf71e13…100c
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 0xa3f6f7c8bd…f22436
Audit this contract →
← previous block·next block →recent activity