← previous blocknext block →recent activity
Analyzing
Block #99,247,025
12 transactions · 12 stateful · 2026-08-26 05:36:10 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,247,025 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w38w19w410w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xa322fef7…1e51
0x34b655…2a6f
6 touches
3 conflicts
0xe251ba03…50f8
0x34b655…2a6f
4 touches
1 conflict
0xf2dc7074…4491
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x68dfc6ca…56ac
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xac0b4a0805…e6faae
Audit this contract →
← previous block·next block →recent activity