← previous blocknext block →recent activity
Analyzing
Block #99,270,029
11 transactions · 8 stateful · 2026-08-26 07:31:59 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,270,029 · 11 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
6w07w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88b8a8b4…5e9b
0x34b655…2a6f
4 touches
1 conflict
0x42e917f7…ed8c
0x34b655…2a6f
4 touches
1 conflict
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x878e93ea…7d32
0x34b655…2a6f
4 touches
1 conflict
0x1db5837f…1264
0x34b655…2a6f
2 touches
0 conflicts
0x4b3b06fc…f6e2
0x34b655…2a6f
2 touches
0 conflicts
0x9ae56910…fe50
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 0x88b8a8b4ff…a85e9b
Audit this contract →
← previous block·next block →recent activity