← previous blocknext block →recent activity
Analyzing
Block #99,475,418
27 transactions · 26 stateful · 2026-08-27 00:45:56 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,475,418 · 27 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
1w02w13w06w17w08w110w011w112w115w216w318w219w121w323w424w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b0b6ae5…8cd9
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0x2f139cc0…ae34
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55010ec8…ea31
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x94c9cbb5…1047
0x34b655…2a6f
4 touches
1 conflict
0xb276222e…49c7
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
6 conflicts on slot 0x9b0b6ae5fe…ab8cd9
Audit this contract →
← previous block·next block →recent activity